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>
This commit is contained in:
parent
92323c8c25
commit
9ae3900461
@ -163,6 +163,18 @@ static int nvme_ns_zoned_check_calc_geometry(NvmeNamespace *ns, Error **errp)
|
||||
return -1;
|
||||
}
|
||||
|
||||
if (ns->params.max_active_zones) {
|
||||
if (ns->params.max_open_zones > ns->params.max_active_zones) {
|
||||
error_setg(errp, "max_open_zones (%u) exceeds max_active_zones (%u)",
|
||||
ns->params.max_open_zones, ns->params.max_active_zones);
|
||||
return -1;
|
||||
}
|
||||
|
||||
if (!ns->params.max_open_zones) {
|
||||
ns->params.max_open_zones = ns->params.max_active_zones;
|
||||
}
|
||||
}
|
||||
|
||||
if (ns->params.zd_extension_size) {
|
||||
if (ns->params.zd_extension_size & 0x3f) {
|
||||
error_setg(errp,
|
||||
|
Loading…
Reference in New Issue
Block a user