aboutsummaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorJohn Berg <jhnberg@amazon.com>2024-04-04 13:04:18 +0100
committerKlaus Jensen <k.jensen@samsung.com>2024-07-11 17:05:37 +0200
commitbc432bc522f5f4ab57e8994d63be41ba20f95b37 (patch)
treea391c5598d70eb4784b901c20176cc610f5fe7dc /scripts
parent59084feb256c617063e0dbe7e64821ae8852d7cf (diff)
downloadqemu-bc432bc522f5f4ab57e8994d63be41ba20f95b37.zip
qemu-bc432bc522f5f4ab57e8994d63be41ba20f95b37.tar.gz
qemu-bc432bc522f5f4ab57e8994d63be41ba20f95b37.tar.bz2
hw/nvme: Add support for setting the MQES for the NVMe emulation
The MQES field in the CAP register describes the Maximum Queue Entries Supported for the IO queues of an NVMe controller. Adding a +1 to the value in this field results in the total queue size. A full queue is when a queue of size N contains N - 1 entries, and the minimum queue size is 2. Thus the lowest MQES value is 1. This patch adds the new mqes property to the NVMe emulation which allows a user to specify the maximum queue size by setting this property. This is useful as it enables testing of NVMe controller where the MQES is relatively small. The smallest NVMe queue size supported in NVMe is 2 submission and completion entries, which means that the smallest legal mqes value is 1. The following example shows how the mqes can be set for a the NVMe emulation: -drive id=nvme0,if=none,file=nvme.img,format=raw -device nvme,drive=nvme0,serial=foo,mqes=1 If the mqes property is not provided then the default mqes will still be 0x7ff (the queue size is 2048 entries). Signed-off-by: John Berg <jhnberg@amazon.co.uk> Reviewed-by: Keith Busch <kbusch@kernel.org> Reviewed-by: Klaus Jensen <k.jensen@samsung.com> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions