[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <EAD49B06-6234-42D7-803F-B764BC82AA3F@suse.de>
Date: Fri, 8 Apr 2011 14:27:23 +0200
From: Alexander Graf <agraf@...e.de>
To: Jan Kiszka <jan.kiszka@...mens.com>
Cc: Cyrill Gorcunov <gorcunov@...il.com>,
Pekka Enberg <penberg@...nel.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Ingo Molnar <mingo@...e.hu>, Avi Kivity <avi@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"aarcange@...hat.com" <aarcange@...hat.com>,
"mtosatti@...hat.com" <mtosatti@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"joro@...tes.org" <joro@...tes.org>,
"asias.hejun@...il.com" <asias.hejun@...il.com>
Subject: Re: [ANNOUNCE] Native Linux KVM tool
On 08.04.2011, at 12:42, Jan Kiszka wrote:
> On 2011-04-08 11:32, Cyrill Gorcunov wrote:
>> It seems there is a misunderstanding. KVM-tool is quite far from been KVM
>> replacement (if ever). And what we're doing -- extremely tiny/small HV which
>> would help us to debug/test kernel code.
>
> I think your core team may have this vision, but my impression is that
> some people here think much further.
I tend to agree. The core team seems to write this as a helping aid of learning the platform and getting to know KVM. I really like that approach :).
However, if it's meant to be a "toy" (and I don't mean this negatively in any way), it really should be declared as such. Calling it "kvm" for example would be a huge mistake in that case.
Either way, I like the idea of having a second user space available for x86. Even if it just means that it verifies that the documentation is correct :).
Alex
--
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