diff options
| author | Sean Brogan <sean.brogan@microsoft.com> | 2019-09-03 16:52:26 -0700 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2019-11-20 02:47:19 +0000 |
| commit | 7607174192166dd5d2d6913fc2fdb8ce539cd3c9 (patch) | |
| tree | c28e164d64ff6d1e89c895b09eb5b5358f6ccd9a /BaseTools/Source/Python/Workspace/MetaDataTable.py | |
| parent | 0b9ad0bc030bbd79073a26fc9b3527ff9128b9da (diff) | |
| download | edk2-7607174192166dd5d2d6913fc2fdb8ce539cd3c9.tar.gz edk2-7607174192166dd5d2d6913fc2fdb8ce539cd3c9.tar.bz2 edk2-7607174192166dd5d2d6913fc2fdb8ce539cd3c9.zip | |
MdeModulePkg/NvmExpressDxe: Fix wrong queue size for async IO queues
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2118
When a packet is queued/completed for the asynchronous IO queue, the logic
to roll over to the front of the queue doesn't account for actual size of
the IO Submission/Completion queue.
This causes a device to hang due to doorbell being outside of visible
queue. An example would be if an NVMe drive only supported a queue size of
128 while the driver supports 256.
Cc: Jian J Wang <jian.j.wang@intel.com>
Signed-off-by: Sean Brogan <sean.brogan@microsoft.com>
Signed-off-by: Hao A Wu <hao.a.wu@intel.com>
Acked-by: Ray Ni <ray.ni@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Workspace/MetaDataTable.py')
0 files changed, 0 insertions, 0 deletions