Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 8 Apr 2022 14:01:16 +0300
From:   "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To:     Sean Christopherson <seanjc@google.com>
Cc:     Dave Hansen <dave.hansen@intel.com>, tglx@linutronix.de,
        mingo@redhat.com, bp@alien8.de, luto@kernel.org,
        peterz@infradead.org, sathyanarayanan.kuppuswamy@linux.intel.com,
        aarcange@redhat.com, ak@linux.intel.com, dan.j.williams@intel.com,
        david@redhat.com, hpa@zytor.com, jgross@suse.com,
        jmattson@google.com, joro@8bytes.org, jpoimboe@redhat.com,
        knsathya@kernel.org, pbonzini@redhat.com, sdeep@vmware.com,
        tony.luck@intel.com, vkuznets@redhat.com, wanpengli@tencent.com,
        thomas.lendacky@amd.com, brijesh.singh@amd.com, x86@kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCHv8 00/30] TDX Guest: TDX core support
Message-ID: <20220408110116.bog3cdtig6entvjh@black.fi.intel.com>
References: <20220405232939.73860-1-kirill.shutemov@linux.intel.com>
 <b43720c6-0763-f4bb-64a0-7745c6ad920a@intel.com>
 <Yk8WZn+etpj/o0OM@google.com>
 <20220407174744.cskt3rg63io4lkug@black.fi.intel.com>
 <Yk8zEN9bZKiQltcL@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Yk8zEN9bZKiQltcL@google.com>
Precedence: bulk

On Thu, Apr 07, 2022 at 06:53:04PM +0000, Sean Christopherson wrote:
> On Thu, Apr 07, 2022, Kirill A. Shutemov wrote:
> > On Thu, Apr 07, 2022 at 04:50:46PM +0000, Sean Christopherson wrote:
> > > On Thu, Apr 07, 2022, Dave Hansen wrote:
> > > > It would also be really nice to get some SEV folks on the list as
> > > > well.  I suspect the coco/ directory will grow more common SEV/TDX
> > > > code over time.
> > > > 
> > > > X86 CONFIDENTIAL COMPUTING
> > > > M:      x86@kernel.org
> > > > R:	Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > > > ...
> > > > S:      Supported
> > > > F:      arch/x86/coco/
> > > > ...
> > > 
> > > And/or a dedicated vger list?
> > 
> > We already have linux-coco@lists.linux.dev. Although, it is not
> > x86-specific.
> 
> Is it ok to spam that list with TDX/SNP stuff, or would it be better to create
> something x86-specific?

In this case the existing coco mailing list will have little to none use
as most of coco traffic is x86-specific at the moment. We can split off
x86-specific later if needed.

-- 
 Kirill A. Shutemov