From 20b5279fb8afc1fe5b5a0700ff31c6b9dc0d89c6 Mon Sep 17 00:00:00 2001
From: =?utf8?q?=E4=B8=81=E5=89=91?= <djukyo@gmail.com>
Date: Sun, 19 Feb 2023 15:43:07 +0800
Subject: [PATCH] log: high latency timestamp issue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

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>
---
 plugins/memblaze/memblaze-nvme.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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;
-- 
2.50.1