[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54E5C16D.3060109@oracle.com>
Date: Thu, 19 Feb 2015 05:56:45 -0500
From: Sasha Levin <sasha.levin@...cle.com>
To: Andre Przywara <andre.przywara@....com>,
Pekka Enberg <penberg@...nel.org>,
Cyrill Gorcunov <gorcunov@...il.com>,
Asias He <asias.hejun@...il.com>
CC: "kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Marc Zyngier <Marc.Zyngier@....com>,
Will Deacon <will.deacon@....com>,
Ronald Minnich <rminnich@...gle.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: stand-alone kvmtool
On 02/13/2015 05:39 AM, Andre Przywara wrote:
> Hi,
>
> as I found it increasingly inconvenient to use kvmtool[1] as part of a
> Linux repository, I decided to give it a go and make it a stand-alone
> project. So I filtered all the respective commits, adjusted the paths in
> there (while keeping authorship and commit date, of course) and then
> added the missing bits to let it compile without a kernel tree nearby.
> The result is now available on:
>
> git://linux-arm.org/kvmtool.git
> http://linux-arm.org/kvmtool.git
Hi Andre,
What inconvenience is caused by having it sit inside the kernel tree
beyond an increased requirement in disk space?
Moving it out will make us lose all the new features and bug fixes we
gain from using the kernel code directly rather than copying it once
in a while.
With your suggestion we'll end up needing something that copies stuff
from the kernel into that standalone tree, just like what qemu does.
Thanks,
Sasha
--
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