From: Sean Christopherson <seanjc@google.com>
To: kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] PUCK Agenda - 2023.06.28 - CANCELED
Date: Tue, 27 Jun 2023 16:06:54 -0700 [thread overview]
Message-ID: <20230627230654.2934968-1-seanjc@google.com> (raw)
No topic this week, and I need to reclaim some time this week as I will be OOO
all of next week.
For future topics, a few things on my radar that I am hoping to discuss in the
not-too-distant future, but that need additional work before they're worth
discussing:
- Coordinating guest_mem() development. I need to post patches, plan is to do
that the week after I get back.
- Overhauling KVM's gfn_to_pfn() APIs. Need a status update from David S., e.g.
I don't even know if this being actively worked.
https://lore.kernel.org/all/ZGvUsf7lMkrNDHuE@google.com
- KVM + UFFD scalability. We're not yet at the point where we need a synchronous
discussion, but I suspect we'll want a live discussion before merging.
https://lore.kernel.org/all/20230602161921.208564-1-amoorthy@google.com
- Hiding KVM internals from the kernel at large, e.g. moving kvm_host.h into
arch/<arch>/kvm and virt/kvm/, and exporting "internal" KVM symbols if and
only if there are vendor modules. Needs an RFC from us (Google GCE people).
Future Schedule:
June 28th - Canceled
July 5th - Canceled (Sean OOO)
July 12th - Available!
July 19th - Available!
next reply other threads:[~2023-06-27 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 23:06 Sean Christopherson [this message]
2023-06-29 21:10 ` 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=20230627230654.2934968-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®