From: Roman Kisel <romank@linux.microsoft.com>
To: Dexuan Cui <decui@microsoft.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"open list:Hyper-V/Azure CORE AND DRIVERS"
<linux-hyperv@vger.kernel.org>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] clocksource: hyper-v: Use lapic timer in a TDX VM without paravisor
Date: Thu, 20 Jun 2024 12:23:06 -0700 [thread overview]
Message-ID: <d0382b2a-2d8f-45f3-a29b-0bd49103a182@linux.microsoft.com> (raw)
In-Reply-To: <20240619002504.3652-1-decui@microsoft.com>
On 6/18/2024 5:25 PM, Dexuan Cui wrote:
> In a TDX VM without paravisor, currently the default timer is the Hyper-V
> timer, which depends on the slow VM Reference Counter MSR: the Hyper-V TSC
> page is not enabled in such a VM because the VM uses Invariant TSC as a
> better clocksource and it's challenging to mark the Hyper-V TSC page shared
> in very early boot.
>
> Lower the rating of the Hyper-V timer so the local APIC timer becomes the
> the default timer in such a VM. This change should cause no perceivable
> performance difference.
>
> Cc: stable@vger.kernel.org # 6.6+
> Signed-off-by: Dexuan Cui <decui@microsoft.com>
> ---
> arch/x86/kernel/cpu/mshyperv.c | 6 +++++-
> drivers/clocksource/hyperv_timer.c | 16 +++++++++++++++-
> 2 files changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
> index e0fd57a8ba840..745af47ca0459 100644
> --- a/arch/x86/kernel/cpu/mshyperv.c
> +++ b/arch/x86/kernel/cpu/mshyperv.c
> @@ -449,9 +449,13 @@ static void __init ms_hyperv_init_platform(void)
> ms_hyperv.hints &= ~HV_X64_APIC_ACCESS_RECOMMENDED;
>
> if (!ms_hyperv.paravisor_present) {
> - /* To be supported: more work is required. */
> + /* Use Invariant TSC as a better clocksource. */
> ms_hyperv.features &= ~HV_MSR_REFERENCE_TSC_AVAILABLE;
>
> + /* Use the Ref Counter in case Invariant TSC is unavailable. */
> + if (!(ms_hyperv.features & HV_ACCESS_TSC_INVARIANT))
> + pr_warn("Hyper-V: Invariant TSC is unavailable\n");
> +
> /* HV_MSR_CRASH_CTL is unsupported. */
> ms_hyperv.misc_features &= ~HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE;
>
> diff --git a/drivers/clocksource/hyperv_timer.c b/drivers/clocksource/hyperv_timer.c
> index b2a080647e413..99177835cadec 100644
> --- a/drivers/clocksource/hyperv_timer.c
> +++ b/drivers/clocksource/hyperv_timer.c
> @@ -137,7 +137,21 @@ static int hv_stimer_init(unsigned int cpu)
> ce->name = "Hyper-V clockevent";
> ce->features = CLOCK_EVT_FEAT_ONESHOT;
> ce->cpumask = cpumask_of(cpu);
> - ce->rating = 1000;
> +
> + /*
> + * Lower the rating of the Hyper-V timer in a TDX VM without paravisor,
> + * so the local APIC timer (lapic_clockevent) is the default timer in
> + * such a VM. The Hyper-V timer is not preferred in such a VM because
> + * it depends on the slow VM Reference Counter MSR (the Hyper-V TSC
> + * page is not enbled in such a VM because the VM uses Invariant TSC
> + * as a better clocksource and it's challenging to mark the Hyper-V
> + * TSC page shared in very early boot).
> + */
> + if (!ms_hyperv.paravisor_present && hv_isolation_type_tdx())
> + ce->rating = 90;
> + else
> + ce->rating = 1000;
> +
> ce->set_state_shutdown = hv_ce_shutdown;
> ce->set_state_oneshot = hv_ce_set_oneshot;
> ce->set_next_event = hv_ce_set_next_event;
LGTM.
Reviewed-by: Roman Kisel <romank@linux.microsoft.com>
--
Thank you,
Roman
next prev parent reply other threads:[~2024-06-20 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 0:25 [PATCH] clocksource: hyper-v: Use lapic timer in a TDX VM without paravisor Dexuan Cui
2024-06-20 19:23 ` Roman Kisel [this message]
2024-06-20 21:18 ` Michael Kelley
2024-06-20 23:00 ` Dexuan Cui
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=d0382b2a-2d8f-45f3-a29b-0bd49103a182@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).