| commit | 9ae390046164e8b62fbdc48d2c6de8ee6fbd3cdc | |
| author | Klaus Jensen <k.jensen@samsung.com> | |
| Tue, 26 Jan 2021 11:32:29 +0000 (26 12:32 +0100) | ||
| committer | Klaus Jensen <k.jensen@samsung.com> | |
| Tue, 9 Mar 2021 10:00:57 +0000 (9 11:00 +0100) | ||
| tree | e66725487e3dba069f56e4b73dd4c41677f533c6 | treesnapshot (tar.gz zip) |
| parent | 92323c8c2566b8ea4cdfe8e72a22d2651b0ee6af | commitdiff |
hw/block/nvme: add missing mor/mar constraint checks
Firstly, if zoned.max_active is non-zero, zoned.max_open must be less
than or equal to zoned.max_active.
Secondly, if only zones.max_active is set, we have to explicitly set
zones.max_open or we end up with an invalid MAR/MOR configuration. This
is an artifact of the parameters not being zeroes-based like in the
spec.
Cc: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Reported-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Reviewed-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Firstly, if zoned.max_active is non-zero, zoned.max_open must be less
than or equal to zoned.max_active.
Secondly, if only zones.max_active is set, we have to explicitly set
zones.max_open or we end up with an invalid MAR/MOR configuration. This
is an artifact of the parameters not being zeroes-based like in the
spec.
Cc: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Reported-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Reviewed-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
| hw/block/nvme-ns.c | diffblobblamehistory |