[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c49061d-eb84-032e-8dcb-dd36a891ce90@intel.com>
Date: Fri, 24 Apr 2020 14:24:11 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Mike Stunes <mstunes@...are.com>, joro@...tes.org
Cc: dan.j.williams@...el.com, dave.hansen@...ux.intel.com,
hpa@...or.com, jgross@...e.com, jroedel@...e.de, jslaby@...e.cz,
keescook@...omium.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, luto@...nel.org,
peterz@...radead.org, thellstrom@...are.com,
thomas.lendacky@....com, virtualization@...ts.linux-foundation.org,
x86@...nel.org,
Sean Christopherson <sean.j.christopherson@...el.com>
Subject: Re: [PATCH] Allow RDTSC and RDTSCP from userspace
On 4/24/20 2:03 PM, Mike Stunes wrote:
> I needed to allow RDTSC(P) from userspace and in early boot in order to
> get userspace started properly. Patch below.
>
> ---
> SEV-ES guests will need to execute rdtsc and rdtscp from userspace and
> during early boot. Move the rdtsc(p) #VC handler into common code and
> extend the #VC handlers.
Do SEV-ES guests _always_ #VC on rdtsc(p)?
Powered by blists - more mailing lists