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 Notes - 2023.07.19 - LPC and guest_memfd
Date: Mon, 24 Jul 2023 09:34:26 -0700 [thread overview]
Message-ID: <20230724163426.13283-1-seanjc@google.com> (raw)
I forgot to hit "record", so unfortunately there's no video evidence this time
around :-(
LPC:
- Format will utilize flexible timeslots; tentatively planning on ~3 "big"
slots of ~40 minutes each, and ~6 "small" slots of 10-15 minutes each.
- Schedule will be announced around September 15th (though that may get pushed
backed to October 1st).
- Schedule is flexibile up until the conference, e.g. if code is merged between
September 15th and early November and obviates the need for a discussion.
guest_memfd:
Topic Branch:
- Work will be coordinated through a dedicated topic branch (likely
kvm-x86/guest_memfd).
- Mostly stable branch; plan is to not rebase it for at least the next month
- Fixes (use Fixes: tag!!!) will be applied on top and squashed when the
branch is rebased.
- TBD will post a series for broader review in a month or so once
development has settled down.
TODO:
- Documentation [Sean?]
- Changelogs [Sean]
- Non-filemap implementation [Paolo]
- Hugepage tests (verify KVM actually installs hugepages as expected)
- Memory failure tests (e.g. synthetic #MC injection)
- Get Input from IOMMU / VFIO [Paolo]
Opens:
- .release_folio and .invalidate_folio versus .evict_inode [Mike]
- Fully anonymous inode vs. proper filesystem [Sean / Paolo]
- HugeTLB (or something similar) support [Future]
- Intrahost migration support [Google GCE]
- NUMA support [ TBD - implement fbind() ]
- Memory Accounting [Sean - should Just Work, keyword should ]
- Page Table Accounting - Should we? [Nikunj]
Recording:
/facepalm
reply other threads:[~2023-07-24 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230724163426.13283-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®