On Tue, Feb 11, 2020 at 07:48:12PM -0800, Andy Lutomirski wrote:
>
>
> > On Feb 11, 2020, at 5:53 AM, Joerg Roedel wrote:
>
> >
> >
> >* Putting some NMI-load on the guest will make it crash usually
> > within a minute
>
> Suppose you do CPUID or some MMIO and get #VC. You fill in t
On Tue, Feb 11, 2020 at 02:12:04PM -0800, Andy Lutomirski wrote:
> On Tue, Feb 11, 2020 at 7:43 AM Joerg Roedel wrote:
> >
> > On Tue, Feb 11, 2020 at 03:50:08PM +0100, Peter Zijlstra wrote:
> >
> > > Oh gawd; so instead of improving the whole NMI situation, AMD went and
> > > made it worse still
> On Feb 11, 2020, at 5:53 AM, Joerg Roedel wrote:
>
>
>* Putting some NMI-load on the guest will make it crash usually
> within a minute
Suppose you do CPUID or some MMIO and get #VC. You fill in the GHCB to ask for
help. Some time between when you start filling it out and when yo
On Tue, Feb 11, 2020 at 7:43 AM Joerg Roedel wrote:
>
> On Tue, Feb 11, 2020 at 03:50:08PM +0100, Peter Zijlstra wrote:
>
> > Oh gawd; so instead of improving the whole NMI situation, AMD went and
> > made it worse still ?!?
>
> Well, depends on how you want to see it. Under SEV-ES an IRET will no
On Tue, Feb 11, 2020 at 03:50:08PM +0100, Peter Zijlstra wrote:
> Oh gawd; so instead of improving the whole NMI situation, AMD went and
> made it worse still ?!?
Well, depends on how you want to see it. Under SEV-ES an IRET will not
re-open the NMI window, but the guest has to tell the hypervis
On Tue, Feb 11, 2020 at 02:51:54PM +0100, Joerg Roedel wrote:
> NMI Special Handling
>
>
> The last thing that needs special handling with SEV-ES are NMIs.
> Hypervisors usually start to intercept IRET instructions when an NMI got
> injected to find out when the NMI window is
Hi,
here is the first public post of the patch-set to enable Linux to run
under SEV-ES enabled hypervisors. The code is mostly feature-complete,
but there are still a couple of bugs to fix. Nevertheless, given the
size of the patch-set, I think it is about time to ask for initial
feedback of the c
