From: "Gowans, James" <jgowans@amazon.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "maz@kernel.org" <maz@kernel.org>, "Graf (AWS),
Alexander" <graf@amazon.de>,
"seanjc@google.com" <seanjc@google.com>,
"Saenz Julienne, Nicolas" <nsaenz@amazon.es>
Subject: Re: [ANNOUNCE] KVM Microconference at LPC 2023
Date: Fri, 26 May 2023 15:24:17 +0000 [thread overview]
Message-ID: <88db2d9cb42e471692ff1feb0b9ca855906a9d95.camel@amazon.com> (raw)
In-Reply-To: <2f19f26e-20e5-8198-294e-27ea665b706f@redhat.com>
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.
2. Supporting more fine-grain memory management and access control APIs
for the virtualisation case specifically, for use-cases around live
migration, memory oversubscription, and "side-car" virtual machines. These
use cases would benefit from kernel support for things like dynamically
updating IOMMU and MMU permissions independently at fine granularity, all
without actually modifying the VMAs, to support fine-grain handling. And
linking this topic to the one above: being able to do these things when
not backed by struct pages. (There may be some overlap with "KVM guest
private memory" [2] here...)
Would definitely be keen on this MC!
JG
[1] https://lore.kernel.org/linux-mm/a4f62a8e1b0f43db005cc1117c06c00e6c0c85ff.camel@amazon.com/T/#m20c6df3d755cb79b6c426f7d9a02cec37d21e73e
[2] https://lore.kernel.org/lkml/20221202061347.1070246-1-chao.p.peng@linux.intel.com/T/
next prev parent reply other threads:[~2023-05-26 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 9:55 Paolo Bonzini
2023-05-26 15:24 ` Gowans, James [this message]
2023-05-26 16:39 ` Sean Christopherson
2023-05-26 17:08 ` Sean Christopherson
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=88db2d9cb42e471692ff1feb0b9ca855906a9d95.camel@amazon.com \
--to=jgowans@amazon.com \
--cc=graf@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nsaenz@amazon.es \
--cc=pbonzini@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
all inboxes | Powered by JetHome®