From: Dave Hansen <dave.hansen@intel.com>
To: Isaku Yamahata <isaku.yamahata@gmail.com>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, x86@kernel.org,
linux-kernel@vger.kernel.org, thomas.lendacky@amd.com,
brijesh.singh@amd.com, kirill.shutemov@linux.intel.com,
hpa@zytor.com, pbonzini@redhat.com, seanjc@google.com,
srutherford@google.com, ashish.kalra@amd.com,
darren.kenny@oracle.com, venu.busireddy@oracle.com,
boris.ostrovsky@oracle.com, kvm@vger.kernel.org
Subject: Re: [RFC 0/3] Expose Confidential Computing capabilities on sysfs
Date: Tue, 15 Mar 2022 06:30:44 -0700 [thread overview]
Message-ID: <314aea98-7054-09aa-042d-a91796dcbd43@intel.com> (raw)
In-Reply-To: <20220314224346.GA3426703@ls.amr.corp.intel.com>
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.
prev parent reply other threads:[~2022-03-15 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 22:06 Alejandro Jimenez
2022-03-09 22:06 ` [RFC 1/3] x86: Expose Secure Memory Encryption capabilities in sysfs Alejandro Jimenez
2022-03-09 22:06 ` [RFC 2/3] x86: Expose SEV " Alejandro Jimenez
2022-03-09 22:06 ` [RFC 3/3] x86: Expose SEV-ES " Alejandro Jimenez
2022-03-09 22:40 ` [RFC 0/3] Expose Confidential Computing capabilities on sysfs Dave Hansen
2022-03-10 18:07 ` Alejandro Jimenez
2022-03-14 22:43 ` Isaku Yamahata
2022-03-15 1:17 ` Kai Huang
2022-03-15 13:30 ` Dave Hansen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=314aea98-7054-09aa-042d-a91796dcbd43@intel.com \
--to=dave.hansen@intel.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=ashish.kalra@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=darren.kenny@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=srutherford@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=venu.busireddy@oracle.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®