From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Nikolay Borisov <nik.borisov@suse.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-coco@lists.linux.dev, dave.hansen@linux.intel.com,
x86@kernel.org, kirill.shutemov@linux.intel.com
Subject: Re: [RFC PATCH] virt: tdx-guest: Remove quote generation via ioctl
Date: Tue, 23 Jan 2024 19:57:28 +0000 [thread overview]
Message-ID: <ZbAaKAh-230Hj4BF@redhat.com> (raw)
In-Reply-To: <65b00e191087c_37ad29436@dwillia2-xfh.jf.intel.com.notmuch>
On Tue, Jan 23, 2024 at 11:06:01AM -0800, Dan Williams wrote:
> Nikolay Borisov wrote:
> >
> >
> > On 23.01.24 г. 19:51 ч., Kuppuswamy Sathyanarayanan wrote:
> > >
> > > On 1/23/24 8:07 AM, Nikolay Borisov wrote:
> > >> When this driver got merged initially there was no widely agreed upon
> > >> interface how the quote generation interface will work so having an
> > >> ioctl made sense. However, there's now a vendor-neutral interface via
> > >> configfs. Just remove the old ioctl interface and leave only the the
> > >> configfs one.
> > >>
> > >> Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>
> > >> ---
> > >
> > > This ABI allows the user to get the raw report which is further used
> > > for Quote generation via vsock. AFAIK, some vendors (TDX users) and
> > > DCAP user libraries are still using this ABI to support attestation over
> > > vsock model.
> > >
> > > Don't you think we should wait till there are no users before considering
> > > removing it?
> >
> > Given that hw with TDX was just released I'd be surprised if there are
> > any users? But then again, this is an RFC so let's get opinions :)
> >
>
> The assumption is that this tdx_guest_ioctl() ABI has never appeared in
> an enterprise distro kernel. If that assumption is valid, it
> significantly reduces the long term support exposure.
This ioctl is present in current RHEL-9 kernels
https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/blob/main/drivers/virt/coco/tdx-guest/tdx-guest.c?ref_type=heads#L69
and this is exposed to users when running RHEL-9 guest on Azure
cloud with TDX support.
I've not directly checked, but I would assume it is also probably
included in Ubuntu LTS kernels too, since they also target TDX in
Azure.
No idea what the status of SLES is wrt TDX / Azure offhand.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-01-23 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 16:07 [RFC PATCH] virt: tdx-guest: Remove quote generation via ioctl Nikolay Borisov
2024-01-23 17:51 ` Kuppuswamy Sathyanarayanan
2024-01-23 18:24 ` Nikolay Borisov
2024-01-23 19:06 ` Dan Williams
2024-01-23 19:57 ` Daniel P. Berrangé [this message]
2024-01-23 20:09 ` Dan Williams
2024-01-24 11:49 ` Jeremi Piotrowski
2024-01-23 19:09 ` Dionna Amalie Glaze
2024-01-23 19:23 ` Dave Hansen
2024-01-23 20:55 ` Kuppuswamy Sathyanarayanan
2024-01-24 23:44 ` Dan Middleton
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=ZbAaKAh-230Hj4BF@redhat.com \
--to=berrange@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=nik.borisov@suse.com \
--cc=sathyanarayanan.kuppuswamy@linux.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).