From: "Mickaël Salaün" <mic@digikod.net>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
David Stevens <stevensd@chromium.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Huacai Chen <chenhuacai@kernel.org>,
Tianrui Zhao <zhaotianrui@loongson.cn>,
Bibo Mao <maobibo@loongson.cn>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Anup Patel <anup@brainfault.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Xiaoyao Li <xiaoyao.li@intel.com>, Xu Yilun <yilun.xu@intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Fuad Tabba <tabba@google.com>, Jim Mattson <jmattson@google.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Maxim Levitsky <mlevitsk@redhat.com>,
Anish Moorthy <amoorthy@google.com>,
David Matlack <dmatlack@google.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Edgecombe@google.com, Rick P <rick.p.edgecombe@intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Vishal Annapurve <vannapurve@google.com>,
Ackerley Tng <ackerleytng@google.com>,
Maciej Szmigiero <mail@maciej.szmigiero.name>,
Quentin Perret <qperret@google.com>,
Michael Roth <michael.roth@amd.com>,
Wei Wang <wei.w.wang@intel.com>,
Liam Merwick <liam.merwick@oracle.com>,
Isaku Yamahata <isaku.yamahata@gmail.com>,
Kirill Shutemov <kirill.shutemov@linux.intel.com>,
Lai Jiangshan <jiangshan.ljs@antgroup.com>,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Xiong Zhang <xiong.y.zhang@linux.intel.com>,
Jinrong Liang <ljr.kernel@gmail.com>,
Like Xu <like.xu.linux@gmail.com>,
Mingwei Zhang <mizhang@google.com>,
Dapeng Mi <dapeng1.mi@intel.com>,
James Morris <jamorris@linux.microsoft.com>,
"Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>,
Thara Gopinath <tgopinath@microsoft.com>
Subject: Re: [ANNOUNCE] KVM Microconference at LPC 2024
Date: Thu, 4 Apr 2024 20:26:18 +0200 [thread overview]
Message-ID: <20240404.Chie9boy2eef@digikod.net> (raw)
In-Reply-To: <20240402190652.310373-1-seanjc@google.com>
On Tue, Apr 02, 2024 at 12:06:52PM -0700, Sean Christopherson wrote:
> We are planning on submitting a CFP to host a second annual KVM Microconference
> at Linux Plumbers Conference 2024 (https://lpc.events/event/18). To help make
> our submission as strong as possible, please respond if you will likely attend,
> and/or have a potential topic that you would like to include in the proposal.
> The tentative submission is below.
>
> Note! This is extremely time sensitive, as the deadline for submitting is
> April 4th (yeah, we completely missed the initial announcement).
>
> Sorry for the super short notice. :-(
>
> P.S. The Cc list is very ad hoc, please forward at will.
>
> ===================
> KVM Microconference
> ===================
>
> KVM (Kernel-based Virtual Machine) enables the use of hardware features to
> improve the efficiency, performance, and security of virtual machines (VMs)
> created and managed by userspace. KVM was originally developed to accelerate
> VMs running a traditional kernel and operating system, in a world where the
> host kernel and userspace are part of the VM's trusted computing base (TCB).
>
> KVM has long since expanded to cover a wide (and growing) array of use cases,
> e.g. sandboxing untrusted workloads, deprivileging third party code, reducing
> the TCB of security sensitive workloads, etc. The expectations placed on KVM
> have also matured accordingly, e.g. functionality that once was "good enough"
> no longer meets the needs and demands of KVM users.
>
> The KVM Microconference will focus on how to evolve KVM and adjacent subsystems
> in order to satisfy new and upcoming requirements. Of particular interest is
> extending and enhancing guest_memfd, a guest-first memory API that was heavily
> discussed at the 2023 KVM Microconference, and merged in v6.8.
>
> Potential Topics:
> - Removing guest memory from the host kernel's direct map[1]
> - Mapping guest_memfd into host userspace[2]
> - Hugepage support for guest_memfd[3]
> - Eliminating "struct page" for guest_memfd
> - Passthrough/mediated PMU virtualization[4]
> - Pagetable-based Virtual Machine (PVM)[5]
> - Optimizing/hardening KVM usage of GUP[6][7]
> - Defining KVM requirements for hardware vendors
> - Utilizing "fault" injection to increase test coverage of edge cases
We are still working on Heki to improve CR-pinning, memory protection,
related interfaces and tests. We'll send a new patch series shortly on
CR-pinning (only), and follow-ups later. By September, we'll like to
share some updates and this microconference would be a good opportunity,
with the right format this time. ;)
>
> [1] https://lore.kernel.org/all/cc1bb8e9bc3e1ab637700a4d3defeec95b55060a.camel@amazon.com
> [2] https://lore.kernel.org/all/20240222161047.402609-1-tabba@google.com
> [3] https://lore.kernel.org/all/CABgObfa=DH7FySBviF63OS9sVog_wt-AqYgtUAGKqnY5Bizivw@mail.gmail.com
> [4] https://lore.kernel.org/all/20240126085444.324918-1-xiong.y.zhang@linux.intel.com
> [5] https://lore.kernel.org/all/20240226143630.33643-1-jiangshanlai@gmail.com
> [6] https://lore.kernel.org/all/CABgObfZCay5-zaZd9mCYGMeS106L055CxsdOWWvRTUk2TPYycg@mail.gmail.com
> [7] https://lore.kernel.org/all/20240320005024.3216282-1-seanjc@google.com
>
prev parent reply other threads:[~2024-04-04 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:06 [ANNOUNCE] KVM Microconference at LPC 2024 Sean Christopherson
2024-04-03 11:23 ` Sandipan Das
2024-04-03 15:38 ` Will Deacon
2024-04-03 16:12 ` Gupta, Pankaj
2024-04-03 17:40 ` Michael Roth
2024-04-04 0:17 ` Vishal Annapurve
2024-04-04 13:10 ` Lai Jiangshan
2024-04-04 18:26 ` Mickaël Salaün [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=20240404.Chie9boy2eef@digikod.net \
--to=mic@digikod.net \
--cc=Edgecombe@google.com \
--cc=ackerleytng@google.com \
--cc=amoorthy@google.com \
--cc=anup@brainfault.org \
--cc=borntraeger@linux.ibm.com \
--cc=chao.p.peng@linux.intel.com \
--cc=chenhuacai@kernel.org \
--cc=dapeng1.mi@intel.com \
--cc=david@redhat.com \
--cc=dmatlack@google.com \
--cc=frankja@linux.ibm.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=imbrenda@linux.ibm.com \
--cc=isaku.yamahata@gmail.com \
--cc=isaku.yamahata@intel.com \
--cc=james.morse@arm.com \
--cc=jamorris@linux.microsoft.com \
--cc=jarkko@kernel.org \
--cc=jiangshan.ljs@antgroup.com \
--cc=jmattson@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=liam.merwick@oracle.com \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ljr.kernel@gmail.com \
--cc=madvenka@linux.microsoft.com \
--cc=mail@maciej.szmigiero.name \
--cc=maobibo@loongson.cn \
--cc=maz@kernel.org \
--cc=michael.roth@amd.com \
--cc=mizhang@google.com \
--cc=mlevitsk@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=qperret@google.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=stevensd@chromium.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=tgopinath@microsoft.com \
--cc=vannapurve@google.com \
--cc=vbabka@suse.cz \
--cc=wei.w.wang@intel.com \
--cc=xiaoyao.li@intel.com \
--cc=xiong.y.zhang@linux.intel.com \
--cc=yilun.xu@intel.com \
--cc=yu.c.zhang@linux.intel.com \
--cc=yuzenghui@huawei.com \
--cc=zhaotianrui@loongson.cn \
/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