From: Nikunj A Dadhania <nikunj@amd.com>
To: <linux-kernel@vger.kernel.org>, <x86@kernel.org>
Cc: <bp@alien8.de>, <thomas.lendacky@amd.com>,
<dionnaglaze@google.com>, <pgonda@google.com>,
<seanjc@google.com>, <pbonzini@redhat.com>, <nikunj@amd.com>
Subject: [PATCH v3 12/14] x86/kvmclock: Skip kvmclock when Secure TSC is available
Date: Sat, 22 Jul 2023 16:49:07 +0530 [thread overview]
Message-ID: <20230722111909.15166-13-nikunj@amd.com> (raw)
In-Reply-To: <20230722111909.15166-1-nikunj@amd.com>
For AMD SNP guests having Secure TSC enabled, skip using the kvmclock.
The guest kernel will fallback and use Secure TSC based clocksource.
Signed-off-by: Nikunj A Dadhania <nikunj@amd.com>
---
arch/x86/kernel/kvmclock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/kvmclock.c b/arch/x86/kernel/kvmclock.c
index 0f35d44c56fe..1be342064851 100644
--- a/arch/x86/kernel/kvmclock.c
+++ b/arch/x86/kernel/kvmclock.c
@@ -288,7 +288,7 @@ void __init kvmclock_init(void)
{
u8 flags;
- if (!kvm_para_available() || !kvmclock)
+ if (!kvm_para_available() || !kvmclock || cc_platform_has(CC_ATTR_GUEST_SECURE_TSC))
return;
if (kvm_para_has_feature(KVM_FEATURE_CLOCKSOURCE2)) {
--
2.34.1
next prev parent reply other threads:[~2023-07-22 11:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 11:18 [PATCH v3 00/14] Add Secure TSC support for SNP guests Nikunj A Dadhania
2023-07-22 11:18 ` [PATCH v3 01/14] virt: sev-guest: Use AES GCM crypto library Nikunj A Dadhania
2023-08-01 15:32 ` Tom Lendacky
2023-07-22 11:18 ` [PATCH v3 02/14] virt: sev-guest: Move mutex to SNP guest device structure Nikunj A Dadhania
2023-07-22 11:18 ` [PATCH v3 03/14] virt: sev-guest: Replace pr_debug with dev_dbg Nikunj A Dadhania
2023-08-01 15:34 ` Tom Lendacky
2023-08-02 4:08 ` Nikunj A. Dadhania
2023-07-22 11:18 ` [PATCH v3 04/14] virt: sev-guest: Add SNP guest request structure Nikunj A Dadhania
2023-08-01 15:49 ` Tom Lendacky
2023-08-02 4:10 ` Nikunj A. Dadhania
2023-07-22 11:19 ` [PATCH v3 05/14] virt: sev-guest: Add vmpck_id to snp_guest_dev struct Nikunj A Dadhania
2023-08-01 16:30 ` Tom Lendacky
2023-08-02 4:12 ` Nikunj A. Dadhania
2023-08-02 16:55 ` Tom Lendacky
2023-08-03 5:02 ` Nikunj A. Dadhania
2023-07-22 11:19 ` [PATCH v3 06/14] x86/sev: Cache the secrets page address Nikunj A Dadhania
2023-08-01 16:34 ` Tom Lendacky
2023-07-22 11:19 ` [PATCH v3 07/14] x86/sev: Move and reorganize sev guest request api Nikunj A Dadhania
2023-07-22 11:19 ` [PATCH v3 08/14] x86/mm: Add generic guest initialization hook Nikunj A Dadhania
2023-07-22 11:19 ` [PATCH v3 09/14] x86/sev: Add Secure TSC support for SNP guests Nikunj A Dadhania
2023-07-22 11:19 ` [PATCH v3 10/14] x86/sev: Change TSC MSR behavior for Secure TSC enabled guests Nikunj A Dadhania
2023-07-22 11:19 ` [PATCH v3 11/14] x86/sev: Prevent RDTSC/RDTSCP interception " Nikunj A Dadhania
2023-07-22 11:19 ` Nikunj A Dadhania [this message]
2023-07-22 11:19 ` [PATCH v3 13/14] x86/tsc: Mark Secure TSC as reliable clocksource Nikunj A Dadhania
2023-07-22 11:19 ` [PATCH v3 14/14] x86/sev: Enable Secure TSC for SNP guests Nikunj A Dadhania
2023-08-01 4:47 ` [PATCH v3 00/14] Add Secure TSC support " Nikunj A. Dadhania
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=20230722111909.15166-13-nikunj@amd.com \
--to=nikunj@amd.com \
--cc=bp@alien8.de \
--cc=dionnaglaze@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=x86@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
Powered by JetHome