From: Jason Gunthorpe <jgg@nvidia.com>
To: Yan Zhao <yan.y.zhao@intel.com>
Cc: Sean Christopherson <seanjc@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
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>,
Isaku Yamahata <isaku.yamahata@linux.intel.com>,
David Matlack <dmatlack@google.com>,
Marc Zyngier <maz@kernel.org>,
Michael Roth <michael.roth@amd.com>,
Aaron Lewis <aaronlewis@google.com>
Subject: Re: [ANNOUNCE / RFC] PUCK Future Topics
Date: Mon, 8 Jan 2024 20:24:37 -0400 [thread overview]
Message-ID: <20240109002437.GB439767@nvidia.com> (raw)
In-Reply-To: <ZX/bOwVVsnO5OEhI@yzhao56-desk.sh.intel.com>
On Mon, Dec 18, 2023 at 01:40:11PM +0800, Yan Zhao wrote:
> +Jason,
> On Fri, Dec 15, 2023 at 12:13:27PM -0800, Sean Christopherson wrote:
> > On Thu, Dec 14, 2023, Oliver Upton wrote:
> > > On Wed, Dec 13, 2023 at 04:17:53PM -0800, Sean Christopherson 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
> > > > Needs: Paolo, Yan, Oliver, Marc, more ARM folks?
> > >
> > > Can we move this one? I'm traveling 01.08-01.16 and really don't want
> > > to miss this due to jetlag or travel delays.
> >
> > Ya, can do. I'll pencil it in for 01.24.
> >
> > Yan (and others) would 01.31 work for the "TDP MMU for IOMMU" discussion? Or if
> > you think you'll be ready earlier, 01.17 is also available (at least for now).
> Either 01.17 or 01.31 is working for me.
> But looks earlier is better :)
>
> hi Jason,
> Would you like to join the session to discuss "TDP MMU for IOMMU", which is on
> 01.17 or 01.31?
> (6am PDT
> Video: https://meet.google.com/vdb-aeqo-knk
> Phone: https://tel.meet/vdb-aeqo-knk?pin=3003112178656
> )
Yes, I can make the 17 it looks like
Thanks,
Jason
next prev parent reply other threads:[~2024-01-09 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 0:17 [ANNOUNCE / RFC] PUCK Future Topics Sean Christopherson
2023-12-14 3:32 ` Marc Zyngier
2023-12-14 16:34 ` Sean Christopherson
2023-12-14 17:11 ` Oliver Upton
2023-12-15 20:13 ` Sean Christopherson
2023-12-18 5:40 ` Yan Zhao
2024-01-09 0:24 ` Jason Gunthorpe [this message]
2024-01-09 2:18 ` Yan Zhao
2023-12-15 18:54 ` David Matlack
2024-01-08 23:54 ` Michael Roth
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=20240109002437.GB439767@nvidia.com \
--to=jgg@nvidia.com \
--cc=aaronlewis@google.com \
--cc=axelrasmussen@google.com \
--cc=dmatlack@google.com \
--cc=isaku.yamahata@linux.intel.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=michael.roth@amd.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=seanjc@google.com \
--cc=yan.y.zhao@intel.com \
/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.