[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15253a9f-c95d-48c0-c49b-25c8ddf9414e@amd.com>
Date: Tue, 22 Oct 2024 09:56:13 +0530
From: "Nikunj A. Dadhania" <nikunj@....com>
To: Tom Lendacky <thomas.lendacky@....com>, linux-kernel@...r.kernel.org,
bp@...en8.de, x86@...nel.org, kvm@...r.kernel.org
Cc: mingo@...hat.com, tglx@...utronix.de, dave.hansen@...ux.intel.com,
pgonda@...gle.com, seanjc@...gle.com, pbonzini@...hat.com,
Alexey Makhalov <alexey.makhalov@...adcom.com>,
Juergen Gross <jgross@...e.com>, Boris Ostrovsky <boris.ostrovsky@...cle.com>
Subject: Re: [PATCH v13 11/13] tsc: Switch to native sched clock
On 10/21/2024 8:07 PM, Tom Lendacky wrote:
> 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/
Sure, I will update the message.
Regards
Nikunj
Powered by blists - more mailing lists