Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 26 May 2023 10:08:42 -0700
In-Reply-To: <ZHDflnVNGw1fN6VD@google.com>
Mime-Version: 1.0
References: <2f19f26e-20e5-8198-294e-27ea665b706f@redhat.com>
 <88db2d9cb42e471692ff1feb0b9ca855906a9d95.camel@amazon.com> <ZHDflnVNGw1fN6VD@google.com>
Message-ID: <ZHDnmiyCIXFVxzh9@google.com>
Subject: Re: [ANNOUNCE] KVM Microconference at LPC 2023
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>
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

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.