From: Juan Quintela <quintela@redhat.com>
To: kvm-devel <kvm@vger.kernel.org>, qemu-devel@nongnu.org
Subject: KVM call minutes for 2022-02-08
Date: Tue, 08 Feb 2022 16:05:03 +0100 [thread overview]
Message-ID: <87fsot761s.fsf@secure.mitica> (raw)
Minutes for 2022-02-08
----------------------
- Greensocs have patches to convert it as a library
Are upstream intersted?
Phillipe has some patches to allow to load architectures at runtime,
so he only has one binary.
- Greensocs is finishing the patches to do the configuration
They are rebasing
- Changes to startup to allow QMP to start sooner
* Create a new binary to experiment
Once something is done, we can decide what to do
* Make QMP available the sooner possible
* Copying the current one and remove stuff also takes too long
* Markus started and posted an RFC
* He asks to create a new binary
* What should the new binary done
* Idea is that we will do the minimal possible thing on the new
binary, have it on parallel with current one, and we will decide
later to/if remove the current one.
- Paolo will post patches that just create a binary than setup a qmp
socket
- Markus will rebase its RFC on top of that
- Greensocks will post his series to convert QEMU into one library
- PhilMD will post his RFC to enable a single binary for all
architectures
reply other threads:[~2022-02-08 15:05 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=87fsot761s.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.