[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <314aea98-7054-09aa-042d-a91796dcbd43@intel.com>
Date: Tue, 15 Mar 2022 06:30:44 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Isaku Yamahata <isaku.yamahata@...il.com>,
Alejandro Jimenez <alejandro.j.jimenez@...cle.com>
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
x86@...nel.org, linux-kernel@...r.kernel.org,
thomas.lendacky@....com, brijesh.singh@....com,
kirill.shutemov@...ux.intel.com, hpa@...or.com,
pbonzini@...hat.com, seanjc@...gle.com, srutherford@...gle.com,
ashish.kalra@....com, darren.kenny@...cle.com,
venu.busireddy@...cle.com, boris.ostrovsky@...cle.com,
kvm@...r.kernel.org
Subject: Re: [RFC 0/3] Expose Confidential Computing capabilities on sysfs
On 3/14/22 15:43, Isaku Yamahata wrote:
> xfam_fixed0 fixed-0 value for TD xfam value as a
> hexadecimal number with the "0x" prefix.
> xfam_fixed1 fixed-1 value for TD xfam value as a
> hexadecimal number with the "0x" prefix.
I don't think we should be exporting things and creating ABI just for
the heck of it. These are a prime example. XFAM is reported to the
guest in CPUID. Yes, these may be used to help *build* XFAM, but
userspace doesn't need to know how XFAM was built. It just needs to
know what features it can use.
Powered by blists - more mailing lists