From: Tom Lendacky <thomas.lendacky@amd.com>
To: Nikunj A Dadhania <nikunj@amd.com>,
linux-kernel@vger.kernel.org, bp@alien8.de, x86@kernel.org,
kvm@vger.kernel.org
Cc: mingo@redhat.com, tglx@linutronix.de,
dave.hansen@linux.intel.com, pgonda@google.com,
seanjc@google.com, pbonzini@redhat.com,
Alexey Makhalov <alexey.makhalov@broadcom.com>,
Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v13 11/13] tsc: Switch to native sched clock
Date: Mon, 21 Oct 2024 09:37:43 -0500 [thread overview]
Message-ID: <04684b8a-c8a7-5d4d-de8d-16b389d0c64f@amd.com> (raw)
In-Reply-To: <20241021055156.2342564-12-nikunj@amd.com>
On 10/21/24 00:51, Nikunj A Dadhania wrote:
> Although the kernel switches over to stable TSC clocksource instead of PV
> clocksource, the scheduler still keeps on using PV clocks as the sched
> clock source. This is because the following KVM, Xen and VMWare, switches
s/the following//
s/switches/switch/
> the paravirt sched clock handler in their init routines. The HyperV is the
s/The HyperV/HyperV/
> only PV clock source that checks if the platform provides invariant TSC and
s/provides invariant/provides an invariant/
Thanks,
Tom
> does not switch to PV sched clock.
>
> When switching back to stable TSC, restore the scheduler clock to
> native_sched_clock().
>
> As the clock selection happens in the stop machine context, schedule
> delayed work to update the static_call()
>
> Cc: Alexey Makhalov <alexey.makhalov@broadcom.com>
> Cc: Juergen Gross <jgross@suse.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Signed-off-by: Nikunj A Dadhania <nikunj@amd.com>
> ---
> arch/x86/kernel/tsc.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> index 27faf121fb78..38e35cac6c42 100644
> --- a/arch/x86/kernel/tsc.c
> +++ b/arch/x86/kernel/tsc.c
> @@ -272,10 +272,25 @@ bool using_native_sched_clock(void)
> {
> return static_call_query(pv_sched_clock) == native_sched_clock;
> }
> +
> +static void enable_native_sc_work(struct work_struct *work)
> +{
> + pr_info("using native sched clock\n");
> + paravirt_set_sched_clock(native_sched_clock);
> +}
> +static DECLARE_DELAYED_WORK(enable_native_sc, enable_native_sc_work);
> +
> +static void enable_native_sched_clock(void)
> +{
> + if (!using_native_sched_clock())
> + schedule_delayed_work(&enable_native_sc, 0);
> +}
> #else
> u64 sched_clock_noinstr(void) __attribute__((alias("native_sched_clock")));
>
> bool using_native_sched_clock(void) { return true; }
> +
> +void enable_native_sched_clock(void) { }
> #endif
>
> notrace u64 sched_clock(void)
> @@ -1157,6 +1172,10 @@ static void tsc_cs_tick_stable(struct clocksource *cs)
> static int tsc_cs_enable(struct clocksource *cs)
> {
> vclocks_set_used(VDSO_CLOCKMODE_TSC);
> +
> + /* Restore native_sched_clock() when switching to TSC */
> + enable_native_sched_clock();
> +
> return 0;
> }
>
next prev parent reply other threads:[~2024-10-21 14:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 5:51 [PATCH v13 00/13] Add Secure TSC support for SNP guests Nikunj A Dadhania
2024-10-21 5:51 ` [PATCH v13 01/13] x86/sev: Carve out and export SNP guest messaging init routines Nikunj A Dadhania
2024-10-21 7:48 ` Christophe JAILLET
2024-10-22 4:12 ` Nikunj A. Dadhania
2024-10-21 5:51 ` [PATCH v13 02/13] x86/sev: Relocate SNP guest messaging routines to common code Nikunj A Dadhania
2024-10-21 5:51 ` [PATCH v13 03/13] x86/sev: Add Secure TSC support for SNP guests Nikunj A Dadhania
2024-10-21 8:12 ` Christophe JAILLET
2024-10-22 4:15 ` Nikunj A. Dadhania
2024-10-21 5:51 ` [PATCH v13 04/13] x86/sev: Change TSC MSR behavior for Secure TSC enabled guests Nikunj A Dadhania
2024-10-23 3:25 ` Xiaoyao Li
2024-10-24 6:24 ` Nikunj A. Dadhania
2024-10-24 7:31 ` Xiaoyao Li
2024-10-24 10:16 ` Nikunj A. Dadhania
2024-10-21 5:51 ` [PATCH v13 05/13] x86/sev: Prevent RDTSC/RDTSCP interception " Nikunj A Dadhania
2024-10-24 7:56 ` Xiaoyao Li
2024-10-24 8:44 ` Nikunj A. Dadhania
2024-10-24 15:34 ` Xiaoyao Li
2024-10-21 5:51 ` [PATCH v13 06/13] x86/sev: Prevent GUEST_TSC_FREQ MSR " Nikunj A Dadhania
2024-10-21 14:08 ` Tom Lendacky
2024-10-22 4:20 ` Nikunj A. Dadhania
2024-10-21 5:51 ` [PATCH v13 07/13] x86/sev: Mark Secure TSC as reliable clocksource Nikunj A Dadhania
2024-10-21 5:51 ` [PATCH v13 08/13] x86/cpu/amd: Do not print FW_BUG for Secure TSC Nikunj A Dadhania
2024-10-21 5:51 ` [PATCH v13 09/13] tsc: Use the GUEST_TSC_FREQ MSR for discovering TSC frequency Nikunj A Dadhania
2024-10-21 14:33 ` Tom Lendacky
2024-10-22 4:24 ` Nikunj A. Dadhania
2024-10-21 5:51 ` [PATCH v13 10/13] tsc: Upgrade TSC clocksource rating Nikunj A Dadhania
2024-10-21 5:51 ` [PATCH v13 11/13] tsc: Switch to native sched clock Nikunj A Dadhania
2024-10-21 14:37 ` Tom Lendacky [this message]
2024-10-22 4:26 ` Nikunj A. Dadhania
2024-10-21 21:30 ` kernel test robot
2024-10-21 23:03 ` kernel test robot
2024-10-21 5:51 ` [PATCH v13 12/13] x86/kvmclock: Abort SecureTSC enabled guest when kvmclock is selected Nikunj A Dadhania
2024-10-21 15:00 ` Tom Lendacky
2024-10-22 4:28 ` Nikunj A. Dadhania
2024-10-21 5:51 ` [PATCH v13 13/13] x86/sev: Allow Secure TSC feature for SNP guests 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=04684b8a-c8a7-5d4d-de8d-16b389d0c64f@amd.com \
--to=thomas.lendacky@amd.com \
--cc=alexey.makhalov@broadcom.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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