From: Sean Christopherson <seanjc@google.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-coco@lists.linux.dev
Subject: Re: [PATCH 1/3] MAINTAINERS: Update the file list in the TDX entry.
Date: Tue, 8 Jul 2025 07:24:07 -0700 [thread overview]
Message-ID: <aG0qB2OEUmBTKzpY@google.com> (raw)
In-Reply-To: <d38b37c7-70fe-4c94-9ef2-e5d765ca5c79@intel.com>
On Tue, Jul 08, 2025, Dave Hansen wrote:
> On 7/8/25 03:19, Kirill A. Shutemov wrote:
> > @@ -26952,12 +26952,18 @@ L: linux-coco@lists.linux.dev
> > S: Supported
> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/tdx
> > F: Documentation/ABI/testing/sysfs-devices-virtual-misc-tdx_guest
> > +F: Documentation/arch/x86/tdx.rst
> > +F: Documentation/virt/coco/tdx-guest.rst
> > +F: Documentation/virt/kvm/x86/intel-tdx.rst
> > F: arch/x86/boot/compressed/tdx*
> > +F: arch/x86/boot/compressed/tdcall.S
> > F: arch/x86/coco/tdx/
> > -F: arch/x86/include/asm/shared/tdx.h
> > -F: arch/x86/include/asm/tdx.h
> > +F: arch/x86/include/asm/shared/tdx*
> > +F: arch/x86/include/asm/tdx*
> > +F: arch/x86/kvm/vmx/tdx*
> > F: arch/x86/virt/vmx/tdx/
> > -F: drivers/virt/coco/tdx-guest
> > +F: drivers/virt/coco/tdx-guest/
> > +F: tools/testing/selftests/tdx/
>
> That file list is getting a bit long, but it _is_ the truth.
What about adding
K: tdx
instead of listing each file individually? That might also help clarify what's
up for cases where there is overlap, e.g. with KVM, to convey that this is a
"secondary" entry of sorts.
> It's also adding some arch/x86/kvm/vmx/ files, but I assume Sean and
> Paolo will welcome having some more people cc'd on those patches. The
> hyper-v folks have a similar entry.
No objection from me.
> I'll plan to apply this as-is unless someone screams.
next prev parent reply other threads:[~2025-07-08 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 10:19 [PATCH 0/3] MAINTAINERS: Update TDX entry Kirill A. Shutemov
2025-07-08 10:19 ` [PATCH 1/3] MAINTAINERS: Update the file list in the " Kirill A. Shutemov
2025-07-08 14:14 ` Dave Hansen
2025-07-08 14:24 ` Sean Christopherson [this message]
2025-07-08 15:17 ` Dave Hansen
2025-07-09 3:31 ` Xiaoyao Li
2025-07-09 4:26 ` Dave Hansen
2025-07-09 13:31 ` Kirill A. Shutemov
2025-07-09 14:18 ` Xiaoyao Li
2025-07-08 10:19 ` [PATCH 2/3] MAINTAINERS: Add Rick Edgecombe as a TDX reviewer Kirill A. Shutemov
2025-07-08 10:19 ` [PATCH 3/3] MAINTAINERS: Update Kirill Shutemov's email address Kirill A. Shutemov
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=aG0qB2OEUmBTKzpY@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.