block/nvme: Properly display doorbell stride length in trace event
Commit 15b2260bef
("block/nvme: Trace controller capabilities")
misunderstood the doorbell stride value from the datasheet, use
the correct one. The 'doorbell_scale' variable used few lines
later is correct.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210127212137.3482291-2-philmd@redhat.com>
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
This commit is contained in:
parent
0212fa2afd
commit
97b709f32e
@ -745,7 +745,7 @@ static int nvme_init(BlockDriverState *bs, const char *device, int namespace,
|
|||||||
trace_nvme_controller_capability("Contiguous Queues Required",
|
trace_nvme_controller_capability("Contiguous Queues Required",
|
||||||
NVME_CAP_CQR(cap));
|
NVME_CAP_CQR(cap));
|
||||||
trace_nvme_controller_capability("Doorbell Stride",
|
trace_nvme_controller_capability("Doorbell Stride",
|
||||||
2 << (2 + NVME_CAP_DSTRD(cap)));
|
1 << (2 + NVME_CAP_DSTRD(cap)));
|
||||||
trace_nvme_controller_capability("Subsystem Reset Supported",
|
trace_nvme_controller_capability("Subsystem Reset Supported",
|
||||||
NVME_CAP_NSSRS(cap));
|
NVME_CAP_NSSRS(cap));
|
||||||
trace_nvme_controller_capability("Memory Page Size Minimum",
|
trace_nvme_controller_capability("Memory Page Size Minimum",
|
||||||
|
Loading…
Reference in New Issue
Block a user