[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e4b74a9-2de6-4d10-c68f-a41a5ad8c07f@linux.intel.com>
Date: Tue, 18 May 2021 09:00:36 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Dave Hansen <dave.hansen@...el.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>
Cc: Tony Luck <tony.luck@...el.com>,
Kirill Shutemov <kirill.shutemov@...ux.intel.com>,
Kuppuswamy Sathyanarayanan <knsathya@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Raj Ashok <ashok.raj@...el.com>,
Sean Christopherson <seanjc@...gle.com>,
linux-kernel@...r.kernel.org,
Sean Christopherson <sean.j.christopherson@...el.com>
Subject: Re: [RFC v2-fix 1/1] x86/traps: Add #VE support for TDX guest
> No APIC access either?
It's all X2APIC inside TDX which uses MSRs
>
> Also, shouldn't we have at least a:
>
> WARN_ON_ONCE(in_nmi());
>
> if we don't expect (or handle well) #VE in NMIs?
We handle it perfectly fine. It's just not needed.
-Andi
Powered by blists - more mailing lists