[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b4ba9e9-dbf6-a094-0684-e68248050758@redhat.com>
Date: Fri, 21 Aug 2020 11:05:24 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Sean Christopherson <sean.j.christopherson@...el.com>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...el.com>,
Chang Seok Bae <chang.seok.bae@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Sasha Levin <sashal@...nel.org>, kvm@...r.kernel.org,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH] x86/entry/64: Disallow RDPID in paranoid entry if KVM is
enabled
On 21/08/20 10:16, Borislav Petkov wrote:
> On Fri, Aug 21, 2020 at 10:09:01AM +0200, Paolo Bonzini wrote:
>> One more MSR *is* a big deal: KVM's vmentry+vmexit cost is around 1000
>> cycles, adding 100 clock cycles for 2 WRMSRs is a 10% increase.
>
> The kernel uses TSC_AUX so we can't reserve it to KVM either.
KVM only uses TSC_AUX while in kernel space, because the kernel hadn't
used it until now. That's for a good reason:
* if possible, __this_cpu_read(cpu_number) is always faster.
* The kernel can just block preemption at its will and has no need for
the atomic rdtsc+vgetcpu provided by RDTSCP.
So far, the kernel had always used LSL instead of RDPID when
__this_cpu_read was not available. In one place, RDTSCP is used as an
ordered rdtsc but it discards the TSC_AUX value. RDPID is also used in
the vDSO but it isn't kernel space.
Hence the assumption that KVM makes (and has made ever since TSC_AUX was
introduced. What is the difference in speed between LSL and RDPID? I
don't have a machine that has RDPID to test it, unfortunately.
Paolo
Powered by blists - more mailing lists