* KVM call minutes for 2017-03-14
@ 2017-03-20 11:15 Juan Quintela
0 siblings, 0 replies; only message in thread
From: Juan Quintela @ 2017-03-20 11:15 UTC (permalink / raw)
To: QEMU Developer, KVM devel mailing list
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-03-20 11:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-20 11:15 KVM call minutes for 2017-03-14 Juan Quintela
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).