diff options
| author | Keith Busch <kbusch@kernel.org> | 2025-08-01 07:24:57 -0700 |
|---|---|---|
| committer | Klaus Jensen <k.jensen@samsung.com> | 2025-08-11 00:17:38 -0700 |
| commit | 53493c1f836f4dda90a6b5f2fb3d9264918c6871 (patch) | |
| tree | a177453387697cd054465149a52ec7aa88a8dc65 /scripts/dump-guest-memory.py | |
| parent | bc0c24fdb157b014932a5012fe4ccbeba7617f17 (diff) | |
| download | qemu-53493c1f836f4dda90a6b5f2fb3d9264918c6871.zip qemu-53493c1f836f4dda90a6b5f2fb3d9264918c6871.tar.gz qemu-53493c1f836f4dda90a6b5f2fb3d9264918c6871.tar.bz2 | |
hw/nvme: cap MDTS value for internal limitation
The emulated device had let the user set whatever max transfers size
they wanted, including no limit. However the device does have an
internal limit of 1024 segments. NVMe doesn't report max segments,
though. This is implicitly inferred based on the MDTS and MPSMIN values.
IOV_MAX is currently 1024 which 4k PRPs can exceed with 2MB transfers.
Don't allow MDTS values that can exceed this, otherwise users risk
seeing "internal error" status to their otherwise protocol compliant
commands.
Signed-off-by: Keith Busch <kbusch@kernel.org>
Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Diffstat (limited to 'scripts/dump-guest-memory.py')
0 files changed, 0 insertions, 0 deletions