From: Philippe Mathieu-Daudé <phi...@redhat.com> As the 'timestamp' variable is declared as a 48-bit bitfield, we do not need to wrap the sum result.
Signed-off-by: Philippe Mathieu-Daudé <phi...@redhat.com> Reviewed-by: Klaus Jensen <k.jen...@samsung.com> Message-Id: <20201002075716.1657849-1-phi...@redhat.com> Signed-off-by: Laurent Vivier <laur...@vivier.eu> --- hw/block/nvme.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/hw/block/nvme.c b/hw/block/nvme.c index 63078f600920..44fa5b90769b 100644 --- a/hw/block/nvme.c +++ b/hw/block/nvme.c @@ -1280,12 +1280,7 @@ static inline uint64_t nvme_get_timestamp(const NvmeCtrl *n) union nvme_timestamp ts; ts.all = 0; - - /* - * If the sum of the Timestamp value set by the host and the elapsed - * time exceeds 2^48, the value returned should be reduced modulo 2^48. - */ - ts.timestamp = (n->host_timestamp + elapsed_time) & 0xffffffffffff; + ts.timestamp = n->host_timestamp + elapsed_time; /* If the host timestamp is non-zero, set the timestamp origin */ ts.origin = n->host_timestamp ? 0x01 : 0x00; -- 2.26.2