From: quintela@redhat.com
To: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call for 2022-11-15
Date: Mon, 14 Nov 2022 12:47:40 +0100 [thread overview]
Message-ID: <87o7t969lv.fsf@secure.mitica> (raw)
Hi
Please, send any topic that you are interested in covering.
We already have some topics:
Re agenda, see below topics our team would like to discuss:
- QEMU support for kernel/vfio V2 live migration patches
- acceptance of changes required for Grace/Hopper passthrough and vGPU
support
- the migration support is now looking like it will converge on the
6.2 kernel
- tuning GPU migration performance on QEMU/vfio, beyond what the V2 work
delivers
Call details:
By popular demand, a google calendar public entry with it
https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
(Let me know if you have any problems with the calendar entry. I just
gave up about getting right at the same time CEST, CET, EDT and DST).
If you need phone number details, contact me privately
Thanks, Juan.
next reply other threads:[~2022-11-14 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 11:47 quintela [this message]
2022-11-14 21:58 ` KVM call for 2022-11-15 Alex Williamson
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=87o7t969lv.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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