From: Sean Christopherson <seanjc@google.com>
To: James Gowans <jgowans@amazon.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"maz@kernel.org" <maz@kernel.org>,
Alexander Graf <graf@amazon.de>,
Nicolas Saenz Julienne <nsaenz@amazon.es>
Subject: Re: [ANNOUNCE] KVM Microconference at LPC 2023
Date: Fri, 26 May 2023 10:08:42 -0700 [thread overview]
Message-ID: <ZHDnmiyCIXFVxzh9@google.com> (raw)
In-Reply-To: <ZHDflnVNGw1fN6VD@google.com>
On Fri, May 26, 2023, Sean Christopherson wrote:
> On Fri, May 26, 2023, James Gowans wrote:
> > On Tue, 2023-05-09 at 11:55 +0200, Paolo Bonzini wrote:
> > > Hi all!
> > >
> > > We are planning on submitting a CFP to host a KVM Microconference at
> > > Linux Plumbers Conference 2023. To help justify the proposal, we would
> > > like to gather a list of folks that would likely attend, and crowdsource
> > > a list of topics to include in the proposal.
> >
> > Hi Paolo,
> >
> > This MC sounds great! There are two topics I'd be keen to discuss, both in
> > the KVM + memory-management realm:
> >
> > 1. Guest and kernel memory persistence across kexec for live update.
> > Specifically focussing on the host IOMMU pgtable persistence for DMA-
> > passthrough devices to support kexec while guest-driven DMA is still
> > running. There is some discussion happening now about this [1] and
> > hopefully the discussion and prototyping will continue in the run up to
> > LPC.
>
> I don't think a KVM MC conference would be the right venue for this discussion.
> IIUC, KVM does not need to be involved in preserving guest memory or the IOMMU
> page tables.
Ah, I assume the KVM involvement comes from a potentially new filesystem for guest
memory?
5. More "advanced" memory management APIs/ioctls for virtualisation: Being
able to support things like DMA-driven post-copy live migration, memory
oversubscription, carving out chunks of memory from a VM to launch side-
car VMs, more fine-grain control of IOMMU or MMU permissions, etc. This
may be easier to achieve with a new filesystem, rather than coupling to
tempfs semantics and ioctls.
next prev parent reply other threads:[~2023-05-26 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 9:55 [ANNOUNCE] KVM Microconference at LPC 2023 Paolo Bonzini
2023-05-26 15:24 ` Gowans, James
2023-05-26 16:39 ` Sean Christopherson
2023-05-26 17:08 ` Sean Christopherson [this message]
2023-05-26 16:09 ` Mickaël Salaün
2023-06-01 21:52 ` Mickaël Salaün
2023-06-02 0:23 ` Sean Christopherson
2023-06-07 10:13 ` Babis Chalios
2023-06-07 10:37 ` Paolo Bonzini
2023-06-07 12:20 ` Babis Chalios
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=ZHDnmiyCIXFVxzh9@google.com \
--to=seanjc@google.com \
--cc=graf@amazon.de \
--cc=jgowans@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nsaenz@amazon.es \
--cc=pbonzini@redhat.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