From: 丁剑 <djukyo@gmail.com>
Date: Sun, 19 Feb 2023 07:43:07 +0000 (+0800)
Subject: log: high latency timestamp issue
X-Git-Tag: v2.4~45
X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=20b5279fb8afc1fe5b5a0700ff31c6b9dc0d89c6;p=users%2Fsagi%2Fnvme-cli.git

log: high latency timestamp issue

1. The old nvme-cli set-feature uses 32bit to represent timestamp, but the spec definition is 48bit.
2. memblaze made a slight correction to allow for overflow.
3. Now this correction is no longer needed.

Signed-off-by: 丁剑 <djukyo@gmail.com>
---

diff --git a/plugins/memblaze/memblaze-nvme.c b/plugins/memblaze/memblaze-nvme.c
index dba5fe88..6cc03b61 100644
--- a/plugins/memblaze/memblaze-nvme.c
+++ b/plugins/memblaze/memblaze-nvme.c
@@ -707,7 +707,7 @@ static int glp_high_latency(FILE *fdi, char *buf, int buflen, int print)
         }
         else  //  sort
         {
-            timestamp = logEntry->timestampH - 1;
+            timestamp = logEntry->timestampH;
             timestamp = timestamp << 32;
             timestamp += logEntry->timestampL;
             tt = timestamp / 1000;