[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6633cd93cd0bc_138462942@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date: Thu, 2 May 2024 10:29:55 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>
CC: Tom Lendacky <thomas.lendacky@....com>, <linux-kernel@...r.kernel.org>,
<x86@...nel.org>, <linux-coco@...ts.linux.dev>,
<svsm-devel@...onut-svsm.dev>, Thomas Gleixner <tglx@...utronix.de>, "Ingo
Molnar" <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
<dave.hansen@...ux.intel.com>, "H. Peter Anvin" <hpa@...or.com>, "Andy
Lutomirski" <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
"Michael Roth" <michael.roth@....com>, Ashish Kalra <ashish.kalra@....com>
Subject: Re: [PATCH v4 13/15] x86/sev: Take advantage of configfs visibility
support in TSM
Kuppuswamy Sathyanarayanan wrote:
[..]
> Got it. Makes sense. It is simpler to do it this way. I am just
> worried that the vendor driver might mistakenly disable some core
> attributes like inblob, outblob, provider and generation.
Then it gets to keep the pieces it broke.
Powered by blists - more mailing lists