From: Yan Zhao <yan.y.zhao@intel.com>
To: Jason Gunthorpe <jgg@nvidia.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: Tue, 9 Jan 2024 10:18:09 +0800 [thread overview]
Message-ID: <ZZys4SH4I7ggIB2P@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <20240109002437.GB439767@nvidia.com>
On Mon, Jan 08, 2024 at 08:24:37PM -0400, Jason Gunthorpe wrote:
> > 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 a lot!
next prev parent reply other threads:[~2024-01-09 2:47 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
2024-01-09 2:18 ` Yan Zhao [this message]
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=ZZys4SH4I7ggIB2P@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=aaronlewis@google.com \
--cc=axelrasmussen@google.com \
--cc=dmatlack@google.com \
--cc=isaku.yamahata@linux.intel.com \
--cc=jgg@nvidia.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 \
/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