From: Kai Huang <kai.huang@intel.com>
To: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Hans de Goede <hdegoede@redhat.com>,
Mark Gross <mgross@linux.intel.com>
Cc: "H . Peter Anvin" <hpa@zytor.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3 4/4] platform/x86: intel_tdx_attest: Add TDX Guest attestation interface driver
Date: Wed, 20 Apr 2022 10:38:09 +1200 [thread overview]
Message-ID: <5371d2df8940226674f27a7ce950e9ae1468a951.camel@intel.com> (raw)
In-Reply-To: <07ef65c4-708e-1bcf-9a7e-f804acefcc7c@linux.intel.com>
On Tue, 2022-04-19 at 07:00 -0700, Sathyanarayanan Kuppuswamy wrote:
>
> On 4/19/22 1:16 AM, Kai Huang wrote:
> > In fact after slightly thinking more, I think you can split TDREPORT TDCALL
> > support with GetQuote/SetupEventNotifyInterrupt support. The reason is as I
> > said, GetQuote isn't mandatory to support attestation. TD attestation agent can
> > use i.e. vsock, tcp/ip, to communicate to QE directly. Whether kernel needs to
> > support GetQuote is actually arguable.
>
> IMO, we should not use a usage model to categorize "GetQuote" support
> as a mandatory or non-mandatory requirement.
>
> For customers who use VSOCK, they can get away without GetQuote
> TDVMCALL support. But for customers who do not want to use
> VSOCK model, this is a required support. AFAIK, our current customer
> requirement is to use TDVMCALL approach for attestation support.
>
> If your suggestion is to split GetQuote support as separate
> patch to make it easier for review, I am fine with such
> suggestion.
>
I am not saying we should get rid of GetQuote support. If there's customer
wants this with a good reason, we can certainly support it. I understand that
some customer wants to deploy QE in host and don't want additional communication
channel (i.e. vsock) between guest and host, which may add additional attack
window and/or customer's validation resource.
My point is regardless whether we need to support GetQuote, logically this
driver can be split to two parts as I said: 1) basic TDREPORT support to
userspace; 2) additional GetQuote support. And I think there are many benefits
if you do in this way as I commented below.
> >
> > So IMHO you can split this attestation driver into two parts:
> >
> > 1) A "basic" driver which supports reporting TDREPORT to userspace
> > 2) Additional support of GetQuote/SetupEventNotifyInterrupt.
> >
> > The 1) can even be in a single patch (I guess it won't be complicated). It is
> > easy to review (and i.e. can be merged separately), and with it, you will
> > immediately have one way to support attestation.
> >
> > 2) can be reviewed separately, perhaps with one additional Kconfig option (i.e.
> > CONFIG_INTEL_TDX_ATTESTATION_GET_QUOTE). I think this part has most of the
>
>
> GetQuote IOCTL support is a very simple feature support, so, IMO, we
> don't need to complicate it with additional config.
>
> >
Additional Kconfig can reduce attack window by turning it off for people don't
need it. Anyway no strong opinion here.
--
Thanks,
-Kai
next prev parent reply other threads:[~2022-04-19 22:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 22:01 [PATCH v3 0/4] Add TDX Guest Attestation support Kuppuswamy Sathyanarayanan
2022-04-15 22:01 ` [PATCH v3 1/4] x86/tdx: Add tdx_mcall_tdreport() API support Kuppuswamy Sathyanarayanan
2022-04-19 2:29 ` Kai Huang
2022-04-19 3:37 ` Sathyanarayanan Kuppuswamy
2022-04-19 3:51 ` Kai Huang
2022-04-19 3:53 ` Sathyanarayanan Kuppuswamy
2022-04-15 22:01 ` [PATCH v3 2/4] x86/tdx: Add tdx_hcall_get_quote() " Kuppuswamy Sathyanarayanan
2022-04-19 2:59 ` Kai Huang
2022-04-19 4:04 ` Sathyanarayanan Kuppuswamy
2022-04-19 4:40 ` Kai Huang
2022-04-19 5:28 ` Sathyanarayanan Kuppuswamy
2022-04-19 7:21 ` Kai Huang
2022-04-20 3:39 ` Aubrey Li
2022-04-20 7:16 ` Sathyanarayanan Kuppuswamy
2022-04-20 8:08 ` Aubrey Li
2022-04-22 17:24 ` Isaku Yamahata
2022-04-25 3:06 ` Aubrey Li
2022-04-15 22:01 ` [PATCH v3 3/4] x86/tdx: Add TDX Guest event notify interrupt support Kuppuswamy Sathyanarayanan
2022-04-15 22:01 ` [PATCH v3 4/4] platform/x86: intel_tdx_attest: Add TDX Guest attestation interface driver Kuppuswamy Sathyanarayanan
2022-04-19 7:47 ` Kai Huang
2022-04-19 8:13 ` Borislav Petkov
2022-04-19 12:48 ` Sathyanarayanan Kuppuswamy
2022-04-20 22:00 ` Borislav Petkov
2022-04-20 22:09 ` Sathyanarayanan Kuppuswamy
2022-04-21 9:10 ` Borislav Petkov
2022-04-21 14:54 ` Sathyanarayanan Kuppuswamy
2022-04-19 8:16 ` Kai Huang
2022-04-19 14:00 ` Sathyanarayanan Kuppuswamy
2022-04-19 22:38 ` Kai Huang [this message]
2022-04-19 14:13 ` Dave Hansen
2022-04-19 14:19 ` Sathyanarayanan Kuppuswamy
2022-04-19 14:24 ` Dave Hansen
2022-04-19 14:26 ` Sathyanarayanan Kuppuswamy
2022-04-19 22:21 ` Kai Huang
2022-04-19 22:49 ` Dave Hansen
2022-04-19 23:02 ` Kai Huang
2022-04-20 1:20 ` Isaku Yamahata
2022-04-20 1:26 ` Sathyanarayanan Kuppuswamy
2022-04-21 7:04 ` Isaku Yamahata
2022-04-21 14:44 ` Sathyanarayanan Kuppuswamy
2022-04-20 23:18 ` Kai Huang
2022-04-20 23:45 ` Sathyanarayanan Kuppuswamy
2022-04-21 0:11 ` Kai Huang
2022-04-21 2:42 ` Sathyanarayanan Kuppuswamy
2022-04-21 6:57 ` Isaku Yamahata
2022-04-21 10:33 ` Kai Huang
2022-04-21 14:53 ` Sathyanarayanan Kuppuswamy
2022-04-21 16:53 ` Isaku Yamahata
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=5371d2df8940226674f27a7ce950e9ae1468a951.camel@intel.com \
--to=kai.huang@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).