[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E2D1D07.9020009@redhat.com>
Date: Mon, 25 Jul 2011 10:36:39 +0300
From: Avi Kivity <avi@...hat.com>
To: Pekka Enberg <penberg@...nel.org>
CC: Anthony Liguori <anthony@...emonkey.ws>,
torvalds@...ux-foundation.org, mingo@...e.hu,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, gorcunov@...il.com, levinsasha928@...il.com,
asias.hejun@...il.com, prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1
On 07/25/2011 10:27 AM, Pekka Enberg wrote:
> Hi Anthony,
>
> On Mon, Jul 25, 2011 at 4:19 AM, Anthony Liguori<anthony@...emonkey.ws> wrote:
> > lguest already does this and lives in the kernel.
>
> Does Lguest have SMP, usermode networking, and GUI support?
>
IIRC, yes, no, and no.
> On Mon, Jul 25, 2011 at 4:19 AM, Anthony Liguori<anthony@...emonkey.ws> wrote:
> > So purely from a kernel perspective, why have two tools in the tree that do
> > the same thing? Shouldn't you at least unify the userspace with the lguest
> > userspace?
>
> Are you talking about Documentation/lguest/lguest.c? How would you
> suggest we unify our code with that?
It should be easy to have tools/kvm drive lguest - they're both virtio
based. All you need to do is provide yet another ops structure to drive
the two ABIs.
I guess lguest.c has to remain, as point of lguest was a simple teaching
aid for virtualization (which doesn't work very well, as the techniques
it uses are obsolete).
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists