On 05/25/2010 04:25 PM, Anthony Liguori wrote:
Currently if someone wants to add a new block format, they have to
upstream it and wait for a new qemu to be released. With a plugin
API, they can add a new block format to an existing, supported qemu.
Whether we have a plugin or protocol based mechanism to implement
block formats really ends up being just an implementation detail.
True.
In order to implement either, we need to take a subset of block
functionality that we feel we can support long term and expose that.
Right now, that's basically just querying characteristics (like size
and geometry) and asynchronous reads and writes.
Unfortunately, you're right.
A protocol based mechanism has the advantage of being more robust in
the face of poorly written block backends so if it's possible to make
it perform as well as a plugin, it's a preferable approach.
May be hard due to difficulty of exposing guest memory.
Plugins that just expose chunks of QEMU internal state directly (like
BlockDriver) are a really bad idea IMHO.
Also, we don't want to expose all of the qemu API. We should default
the visibility attribute to "hidden" and expose only select functions,
perhaps under their own interface. And no inlines.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
