From: "Kaya, Metin" <metikaya@amazon.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [kvm-unit-tests PATCH 1/2] x86/hyperv: Use correct macro in checking SynIC timer support
Date: Tue, 4 Jan 2022 12:51:02 +0000 [thread overview]
Message-ID: <1641300662336.87966@amazon.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 161 bytes --]
This commit fixes 69d4bf751641520f5b2d8e3f160c63c8966fcd8b. stimer_supported() should use HV_X64_MSR_SYNTIMER_AVAILABLE instead of HV_X64_MSR_SYNIC_AVAILABLE.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-x86-hyperv-Use-correct-macro-in-checking-SynIC-timer.patch --]
[-- Type: text/x-patch; name="0001-x86-hyperv-Use-correct-macro-in-checking-SynIC-timer.patch", Size: 969 bytes --]
From 3e31f7d2b7bfc92ff710e3061b32301f96862b8b Mon Sep 17 00:00:00 2001
From: Metin Kaya <metikaya@amazon.com>
Date: Wed, 22 Dec 2021 18:22:28 +0000
Subject: [kvm-unit-tests PATCH 1/2] x86/hyperv: Use correct macro in checking
SynIC timer support
This commit fixes 69d4bf751641520f5b2d8e3f160c63c8966fcd8b.
stimer_supported() should use HV_X64_MSR_SYNTIMER_AVAILABLE instead of
HV_X64_MSR_SYNIC_AVAILABLE.
Signed-off-by: Metin Kaya <metikaya@amazon.com>
---
x86/hyperv.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x86/hyperv.h b/x86/hyperv.h
index e135221..f2bb7b4 100644
--- a/x86/hyperv.h
+++ b/x86/hyperv.h
@@ -190,7 +190,7 @@ static inline bool synic_supported(void)
static inline bool stimer_supported(void)
{
- return cpuid(HYPERV_CPUID_FEATURES).a & HV_X64_MSR_SYNIC_AVAILABLE;
+ return cpuid(HYPERV_CPUID_FEATURES).a & HV_X64_MSR_SYNTIMER_AVAILABLE;
}
static inline bool hv_time_ref_counter_supported(void)
--
2.32.0
next reply other threads:[~2022-01-04 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:51 Kaya, Metin [this message]
2022-01-04 16:32 ` [kvm-unit-tests PATCH 1/2] x86/hyperv: Use correct macro in checking SynIC timer support Vitaly Kuznetsov
2022-01-04 17:04 ` Kaya, Metin
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=1641300662336.87966@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.