From: Michael Roth <michael.roth@amd.com>
To: Sean Christopherson <seanjc@google.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>, Yan Zhao <yan.y.zhao@intel.com>,
David Matlack <dmatlack@google.com>, <pbonzini@redhat.com>,
<isaku.yamahata@intel.com>
Subject: Re: [ANNOUNCE] PUCK Agenda - 2024.01.17 - TDP MMU for IOMMU
Date: Wed, 24 Jan 2024 12:01:50 -0600 [thread overview]
Message-ID: <20240124180150.blms3z7fqseioult@amd.com> (raw)
In-Reply-To: <ZbFJOyGb21UX6qXn@google.com>
On Wed, Jan 24, 2024 at 09:30:35AM -0800, Sean Christopherson wrote:
> On Mon, Jan 22, 2024, Michael Roth wrote:
> > On Tue, Jan 16, 2024 at 05:06:44PM -0800, Sean Christopherson wrote:
> > > Tomorrow's PUCK topic is utilizing KVM's TDP MMU for IOMMU page tables.
> > >
> > > FYI, I am currently without my normal internet (hooray tethering), and we're
> > > supposed to get a healthy dose of freezing rain tonight, i.e. I might lose power
> > > too. I expect to be able to join even if that happens, but I apologize in
> > > advance if I end up being a no-show.
> > >
> > > https://lore.kernel.org/all/20231202091211.13376-1-yan.y.zhao@intel.com
> > >
> > > Time: 6am PDT
> > > Video: https://meet.google.com/vdb-aeqo-knk
> > > Phone: https://tel.meet/vdb-aeqo-knk?pin=3003112178656
> > >
> > > Calendar: https://calendar.google.com/calendar/u/0?cid=Y182MWE1YjFmNjQ0NzM5YmY1YmVkN2U1ZWE1ZmMzNjY5Y2UzMmEyNTQ0YzVkYjFjN2M4OTE3MDJjYTUwOTBjN2Q1QGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
> > > Drive: https://drive.google.com/drive/folders/1aTqCrvTsQI9T4qLhhLs_l986SngGlhPH?resourcekey=0-FDy0ykM3RerZedI8R-zj4A&usp=drive_link
> > >
> > > Future Schedule:
> > > January 24th - Memtypes for non-coherent DMA
> > > January 31st - Available!
> >
> > Hi Sean,
> >
> > I'd like to propose the following topic for the next available slot:
> >
> > "Finalizing internal guest_memfd APIs needed for SNP (TDX?) upstreaming"
> >
> > There's 2 existing interfaces, gmem_prepare, gmem_invalidate, that are
> > needed by the current SNP patches, and there's some additional background
> > about the design decisions here:
> >
> > https://lore.kernel.org/kvm/20231016115028.996656-1-michael.roth@amd.com/
> >
> > There's also another gmem interface that you recently proposed for handling
> > setting up the initial launch image of SNP guests here that seems like it
> > would have a lot of potential overlap with how gmem_prepare is implemented:
> >
> > https://lore.kernel.org/lkml/ZZ67oJwzAsSvui5U@google.com/
> >
> > I'd like to try to get some clarity on what these should look like in order
> > to be considered acceptable for upstreaming of SNP, and potentially any
> > considerations that need to be taken into account for other users like
> > TDX/pKVM/etc.
>
> I penciled this in for the 31st, let me know if that works for you.
That would be perfect. Thanks!
-Mike
prev parent reply other threads:[~2024-01-24 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 1:06 [ANNOUNCE] PUCK Agenda - 2024.01.17 - TDP MMU for IOMMU Sean Christopherson
2024-01-22 19:36 ` Michael Roth
2024-01-24 17:30 ` Sean Christopherson
2024-01-24 18:01 ` Michael Roth [this message]
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=20240124180150.blms3z7fqseioult@amd.com \
--to=michael.roth@amd.com \
--cc=dmatlack@google.com \
--cc=isaku.yamahata@intel.com \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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.