From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [ANNOUNCE / CFP] KVM Microconference at LPC 2023
Date: Mon, 24 Jul 2023 12:37:00 -0700 [thread overview]
Message-ID: <20230724193700.54825-1-seanjc@google.com> (raw)
We are excited to announce the first KVM MC at Plumbers 2023!
The KVM microconference will focus on KVM itself, as well as KVM's touchpoints
with other kernel subsystems. The purpose of the KVM MC is to supplement KVM
Forum by providing developers with a dedicated vehicle for discussing kernel
internals. Topics that are primarily aimed at something other than KVM are
firmly out of scope and will be rejected. Please consider the Confidential
Computing MC, the VFIO/IOMMU/PCI MC, or KVM Forum 2024 for virtualization topics
that aren't directly related to KVM internals.
The KVM MC will be comprised of ~3 "big" topics, and ~6 (+/-2) "small" topics.
Big topics will be allotted 30-40 minutes, and small topics 10-20 minutes.
Please add a note in your submission if you would like your topic to be
considered for a big slot (consider it a hint to help us rough in the scedule).
Below is a list of *ideas* for topics. Topics that are not on the list are more
than welcome! If we were omniscient, we wouldn't need this CFP!
Note, priority will be given to open problems, i.e. things that have already
been posted/discussed on LKML, but posting before LPC is NOT a hard requirement.
Potential Topics:
- Serving inaccessible/unmappable memory for KVM guests (a.k.a. guest_memfd)
- Optimizing mmu_notifiers, e.g. reducing TLB flushes and spurious zapping
- Supporting multiple KVM modules (for non-disruptive upgrades)
- Improving and hardening KVM+perf interactions
- Implementing arch-agnostic abstractions in KVM (e.g. MMU)
- Defining KVM requirements for hardware vendors
- Utilizing "fault" injection to increase test coverage of edge cases
- KVM vs VFIO (e.g. memory types, a rather hot topic on the ARM side)
Abstracts can be submitted via https://lpc.events/event/17/abstracts. Don't
forget to select "KVM MC" as the track!
Thanks!
next reply other threads:[~2023-07-24 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 19:37 Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-13 18:21 Sean Christopherson
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=20230724193700.54825-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®