[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f021003221110p79db476fpae25f6997b61b0b9@mail.gmail.com>
Date: Mon, 22 Mar 2010 20:10:50 +0200
From: Pekka Enberg <penberg@...helsinki.fi>
To: Avi Kivity <avi@...hat.com>
Cc: "Frank Ch. Eigler" <fche@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Joerg Roedel <joro@...tes.org>,
Anthony Liguori <anthony@...emonkey.ws>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Sheng Yang <sheng@...ux.intel.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
Marcelo Tosatti <mtosatti@...hat.com>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Gleb Natapov <gleb@...hat.com>,
Zachary Amsden <zamsden@...hat.com>, ziteng.huang@...el.com,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"Fr?d?ric Weisbecker" <fweisbec@...il.com>
Subject: Re: [RFC] Unify KVM kernel-space and user-space code into a single
project
On Mon, Mar 22, 2010 at 8:04 PM, Avi Kivity <avi@...hat.com> wrote:
>> That said, pulling 400 KLOC of code into the kernel sounds really
>> excessive. Would we need all that if we just do native virtualization
>> and no actual emulation?
>
> What is native virtualization and no actual emulation?
What I meant with "actual emulation" was running architecture A code
on architecture B what was qemu's traditional use case. So the
question was how much of the 400 KLOC do we need for just KVM on all
the architectures that it supports?
--
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