[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EB7D2C0.80201@redhat.com>
Date: Mon, 07 Nov 2011 14:44:48 +0200
From: Avi Kivity <avi@...hat.com>
To: Pekka Enberg <penberg@...nel.org>
CC: Sasha Levin <levinsasha928@...il.com>,
Gerd Hoffmann <kraxel@...hat.com>,
"kvm@...r.kernel.org list" <kvm@...r.kernel.org>,
qemu-devel Developers <qemu-devel@...gnu.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
Alexander Graf <agraf@...e.de>,
Blue Swirl <blauwirbel@...il.com>,
Américo Wang <xiyou.wangcong@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Qemu-devel] [PATCH] KVM: Add wrapper script around QEMU to test
kernels
On 11/07/2011 02:29 PM, Pekka Enberg wrote:
> Hi Avi,
>
> On Mon, Nov 7, 2011 at 2:26 PM, Avi Kivity <avi@...hat.com> wrote:
> >> tools/power was merged in just 2 versions ago, do you think that
> >> merging that was a mistake?
> >
> > Things like tools/power may make sense, most of the code is tied to the
> > kernel interfaces. tools/kvm is 20k lines and is likely to be 40k+
> > lines or more before it is generally usable. The proportion of the code
> > that talks to the kernel is quite small.
>
> So what do you think about perf then? The amount of code that talks to
> the kernel is much smaller than that of the KVM tool.
Maybe it's outgrown the kernel repo too. Certainly something that has
perl and python integration, a TUI, and one day hopefully a GUI, doesn't
really need the kernel sources.
--
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