Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
Date:   Thu, 14 Dec 2023 16:34:12 +0000
In-Reply-To: <864jglbgsh.wl-maz@kernel.org>
Mime-Version: 1.0
References: <20231214001753.779022-1-seanjc@google.com> <864jglbgsh.wl-maz@kernel.org>
Message-ID: <ZXsuhF5Rns1H53zK@google.com>
Subject: Re: [ANNOUNCE / RFC] PUCK Future Topics
From:   Sean Christopherson <seanjc@google.com>
To:     Marc Zyngier <maz@kernel.org>
Cc:     kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
        Paolo Bonzini <pbonzini@redhat.com>,
        James Houghton <jthoughton@google.com>,
        Peter Xu <peterx@redhat.com>,
        Axel Rasmussen <axelrasmussen@google.com>,
        Oliver Upton <oliver.upton@linux.dev>,
        Isaku Yamahata <isaku.yamahata@linux.intel.com>,
        David Matlack <dmatlack@google.com>,
        Yan Zhao <yan.y.zhao@intel.com>,
        Michael Roth <michael.roth@amd.com>,
        Aaron Lewis <aaronlewis@google.com>,
        Christian Borntraeger <borntraeger@linux.ibm.com>,
        Janosch Frank <frankja@linux.ibm.com>,
        Claudio Imbrenda <imbrenda@linux.ibm.com>,
        Anup Patel <anup@brainfault.org>,
        Atish Patra <atishp@atishpatra.org>,
        Michael Ellerman <mpe@ellerman.id.au>,
        Nicholas Piggin <npiggin@gmail.com>,
        Huacai Chen <chenhuacai@kernel.org>
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

On Thu, Dec 14, 2023, Marc Zyngier wrote:
> On Thu, 14 Dec 2023 00:17:53 +0000,
> Sean Christopherson <seanjc@google.com> wrote:
> > 
> > Hi all!  There are a handful of PUCK topics that I want to get scheduled, and
> > would like your help/input in confirming attendance to ensure we reach critical
> > mass.
> > 
> > If you are on the Cc, please confirm that you are willing and able to attend
> > PUCK on the proposed/tentative date for any topics tagged with your name.  Or
> > if you simply don't want to attend, I suppose that's a valid answer too. :-)
> > 
> > If you are not on the Cc but want to ensure that you can be present for a given
> > topic, please speak up asap if you have a conflict.  I will do my best to
> > accomodate everyone's schedules, and the more warning I get the easier that will
> > be.
> > 
> > Note, the proposed schedule is largely arbitrary, I am not wedded to any
> > particular order.  The only known conflict at this time is the guest_memfd()
> > post-copy discussion can't land on Jan 10th.
> > 
> > Thanks!
> > 
> > 
> > 2024.01.03 - Post-copy for guest_memfd()
> >     Needs: David M, Paolo, Peter Xu, James, Oliver, Aaron
> > 
> > 2024.01.10 - Unified uAPI for protected VMs
> >     Needs: Paolo, Isaku, Mike R
> > 
> > 2024.01.17 - Memtypes for non-coherent MDA
> 
> DMA?

Doh, yes, DMA.

> >     Needs: Paolo, Yan, Oliver, Marc, more ARM folks?
> 
> Do we need anyone from the other architectures? I wouldn't be
> surprised if RISC-V was at least as picky as ARM on that front
> (assuming this really is about DMA and not something else).

Ah, yeah, probably.  I had just heard rumblings about ARM, and so ARM was on my
mind.  I added people from all the other flavors of KVM.