From: "Kaya, Metin" <metikaya@amazon.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [kvm-unit-tests PATCH 2/3] x86/hyperv_clock: print sequence field of reference TSC page
Date: Mon, 24 Jan 2022 16:17:53 +0000 [thread overview]
Message-ID: <1643041073871.99850@amazon.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 57 bytes --]
Having TscSequence in the log message for completeness.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0002-x86-hyperv_clock-print-sequence-field-of-reference-T.patch --]
[-- Type: text/x-patch; name="0002-x86-hyperv_clock-print-sequence-field-of-reference-T.patch", Size: 956 bytes --]
From c9f85d69716dd45c9f7662db4599f9cab2623fa3 Mon Sep 17 00:00:00 2001
From: Metin Kaya <metikaya@amazon.com>
Date: Mon, 24 Jan 2022 10:26:58 +0000
Subject: [PATCH 2/3] x86/hyperv_clock: print sequence field of reference TSC
page
Having TscSequence in the log message for completeness.
Signed-off-by: Metin Kaya <metikaya@amazon.com>
---
x86/hyperv_clock.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/x86/hyperv_clock.c b/x86/hyperv_clock.c
index dcf101a..9c30fbe 100644
--- a/x86/hyperv_clock.c
+++ b/x86/hyperv_clock.c
@@ -181,7 +181,8 @@ int main(int ac, char **av)
exit(1);
}
- printf("scale: %" PRIx64" offset: %" PRId64"\n", shadow.tsc_scale, shadow.tsc_offset);
+ printf("sequence: %u. scale: %" PRIx64" offset: %" PRId64"\n",
+ shadow.tsc_sequence, shadow.tsc_scale, shadow.tsc_offset);
ref1 = rdmsr(HV_X64_MSR_TIME_REF_COUNT);
tsc1 = rdtsc();
t1 = hvclock_tsc_to_ticks(&shadow, tsc1);
--
2.32.0
reply other threads:[~2022-01-24 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1643041073871.99850@amazon.com \
--to=metikaya@amazon.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).