From: Sean Christopherson <seanjc@google.com>
To: Juan Quintela <quintela@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Paul Moore <pmoore@redhat.com>,
peter.maydell@linaro.org
Subject: Re: Fortnightly KVM call for 2023-02-07
Date: Thu, 23 Feb 2023 14:04:39 -0800 [thread overview]
Message-ID: <Y/fi95ksLZSVc9/T@google.com> (raw)
In-Reply-To: <87o7qof00m.fsf@secure.mitica>
On Tue, Jan 24, 2023, Juan Quintela wrote:
> Please, send any topic that you are interested in covering in the next
> call in 2 weeks.
>
> We have already topics:
> - single qemu binary
> People on previous call (today) asked if Markus, Paolo and Peter could
> be there on next one to further discuss the topic.
>
> - Huge Memory guests
>
> Will send a separate email with the questions that we want to discuss
> later during the week.
>
> After discussions on the QEMU Summit, we are going to have always open a
> KVM call where you can add topics.
Hi Juan!
I have a somewhat odd request: can I convince you to rename "KVM call" to something
like "QEMU+KVM call"?
I would like to kickstart a recurring public meeting/forum that (almost) exclusively
targets internal KVM development, but I don't to cause confusion and definitely don't
want to usurp your meeting. The goal/purpose of the KVM-specific meeting would be to
do design reviews, syncs, etc. on KVM internals and things like KVM selftests, while,
IIUC, the current "KVM call" is aimed at at the entire KVM+QEMU+VFIO ecosystem.
Thanks!
next prev parent reply other threads:[~2023-02-23 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 15:03 Fortnightly KVM call for 2023-02-07 Juan Quintela
2023-02-01 18:39 ` Juan Quintela
2023-02-23 22:04 ` Sean Christopherson [this message]
2023-02-24 6:28 ` Markus Armbruster
2023-02-28 11:46 ` Juan Quintela
2023-03-07 16:22 ` 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=Y/fi95ksLZSVc9/T@google.com \
--to=seanjc@google.com \
--cc=armbru@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=pmoore@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).