From: Juan Quintela <quintela@redhat.com>
To: QEMU Developer <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: KVM call minutes for 2017-03-14
Date: Mon, 20 Mar 2017 12:15:18 +0100 [thread overview]
Message-ID: <8760jbu434.fsf@secure.mitica> (raw)
Hi
After a long while, we have had a kvm call.
See the thread for the agenda for things that were discussed. My notes
are a bit clear because I was also partipating.
Please, reply with more things.
- What to do with qemu to evolve?
Making it more modular (seems to be a good idea)
more configurable (decide what we compile in or not)
* xen and kvm can already be compiled out
* there are patches posted for tcg, but not upstream
- how widely use is kvmtool?
- Change to a different language?
* what we want to achieve wit that?
Better support to detect "errors"
Less boilerplate code to have to write
Easier language for writing emulation code
- Can we do anything better than more documentation for people that want
to write a driver?
- Should we use more upstream libraries? Should we develop more inside
qemu?
- Object model?
* Was QOM a good decision? Better to move to glib model?
- Documentation? What format are we going to use
There are patches to be integrated.
- What can we do to help device model writers?
Thanks, Juan.
reply other threads:[~2017-03-20 11:15 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=8760jbu434.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;
as well as URLs for NNTP newsgroup(s).