btw: Rusty, I tried to apply the new-io-lguest* patches and they
failed
to apply cleanly.
What base repo do you use for that?
Sorry, with all the movement of getting lguest in tree, those patches
have rotted slightly (particularly the new-io-lguest-readwrite.patch
which needs a complete
On Wed, 2007-08-15 at 00:52 -0700, Dor Laor wrote:
If the above is followed, any enhancement will be appriciated.
Since I am close, I will probably make at least one more v3 drop as is
with the new lguest_bus inspired pvbus (with hotplug, etc). From there,
we can (virtually) get together and
On Wed, 2007-08-15 at 00:13 -0400, Gregory Haskins wrote:
On Wed, 2007-08-15 at 06:58 +0300, Avi Kivity wrote:
since it wants to be hypervisor agnostic, it cannot specify an ABI (as
some already have ABIs, for example Xen).
I see, and that is a good point. By only being an API, virtio
Since I am close, I will probably make at least one more v3 drop as
is
with the new lguest_bus inspired pvbus (with hotplug, etc). From
there,
we can (virtually) get together and figure out what can be used
directly, what can be used in spirit, and what should be thrown away.
Sure thing.
Dor,
On Wed, 2007-08-15 at 15:37 -0700, Dor Laor wrote:
If you'll be quick enough you can rip the lguest_bus into a very light
weight
virtio_bus. Please keep it thin as possible, Rusty's code is 217 lines
long, half
of it comments. I'm planing to have a flexible use of this bus while one
can
On Wed, 2007-08-15 at 00:52 -0700, Dor Laor wrote:
btw: Rusty, I tried to apply the new-io-lguest* patches and they failed
to apply cleanly.
What base repo do you use for that?
Sorry, with all the movement of getting lguest in tree, those patches
have rotted slightly (particularly the
This series incorporates all of v1 plus the following changes based on
feedback to date:
*) s/ioq_iter/ioq_iter_init
*) removed unecessary desc-offset
*) utilized create_irq() to actually assign interrupt resource
*) removed inadvertant cleanup of whitespace from series
*) added memory
Gregory Haskins wrote:
This series incorporates all of v1 plus the following changes based on
feedback to date:
Are you positioning this as an alternative to virtio? If so, be aware
that virtio is (a) mostly done (b) very well done.
Can you describe what you are trying to achieve that
On Wed, 2007-08-15 at 05:50 +0300, Avi Kivity wrote:
Gregory Haskins wrote:
This series incorporates all of v1 plus the following changes based on
feedback to date:
Are you positioning this as an alternative to virtio?
Absolutely not! I really just want to see a decent PV-IO
Gregory Haskins wrote:
If so, be aware that virtio is (a) mostly done (b) very well done.
I would very much like to help make virtio work, which is really where I
was going with this. My design is a little bit different so I was
submitting it in case there was any ideas worth
On Wed, 2007-08-15 at 05:50 +0300, Avi Kivity wrote:
Gregory Haskins wrote:
This series incorporates all of v1 plus the following changes based on
feedback to date:
Are you positioning this as an alternative to virtio? If so, be aware
that virtio is (a) mostly done (b) very well
11 matches
Mail list logo
