[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2184400d-856e-ed4c-b23d-77b7dfd72658@linux.intel.com>
Date: Wed, 9 Jun 2021 14:42:37 -0700
From: "Kuppuswamy, Sathyanarayanan"
<sathyanarayanan.kuppuswamy@...ux.intel.com>
To: Dan Williams <dan.j.williams@...el.com>,
Dave Hansen <dave.hansen@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>,
Tony Luck <tony.luck@...el.com>,
Andi Kleen <ak@...ux.intel.com>,
Kirill Shutemov <kirill.shutemov@...ux.intel.com>,
Kuppuswamy Sathyanarayanan <knsathya@...nel.org>,
Raj Ashok <ashok.raj@...el.com>,
Sean Christopherson <seanjc@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC v2-fix-v5 1/1] x86: Skip WBINVD instruction for VM guest
On 6/9/21 2:38 PM, Dan Williams wrote:
>> In TDX guests, these WBINVD operations cause #VE exceptions. For debug,
>> it would be ideal for the #VE handler to be able to WARN() when an
>> unexpected WBINVD occurs. (<--- problem #2)
> ...but it doesn't WARN() it triggers unhandled #VE, unless I missed
> another patch that precedes this that turns it into a WARN()? If a
> code path expects WBINVD for correct operation and the guest can't
> execute that sounds fatal, not a WARN to me.
Yes. It is not WARN. It is a fatal unhandled exception.
>
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
Powered by blists - more mailing lists