From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
linux-coco@lists.linux.dev
Cc: 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 12:55:24 -0800 [thread overview]
Message-ID: <b7d0faea-22ec-4a10-9385-295e3fde01cf@linux.intel.com> (raw)
In-Reply-To: <210357bf-2b0b-424e-be2f-119804348c40@intel.com>
On 1/23/24 11:23 AM, Dave Hansen wrote:
> On 1/23/24 09:51, Kuppuswamy Sathyanarayanan wrote:
>> Don't you think we should wait till there are no users before considering
>> removing it?
> If an overwhelming majority of the folks to which Intel has provided
> TDX-capable hardware say that they are not using and will never use the
> ioctl() interface, we should definitely consider removing it.
Got it.
> How many kernels did this ioctl() show up in, btw?
It got merged in v6.2. It should be part of LTS and regular kernel releases >= v6.2
Redhat and ubuntu also merged it in their LTS kernels.
>
> Ideally, we'd get a warning into all those kernels.
>
Agree.
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2024-01-23 20:55 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é
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 [this message]
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=b7d0faea-22ec-4a10-9385-295e3fde01cf@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=dave.hansen@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=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).