From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBacK-0001V1-FO for qemu-devel@nongnu.org; Tue, 02 Jun 2009 16:29:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBacF-0001MT-8T for qemu-devel@nongnu.org; Tue, 02 Jun 2009 16:29:51 -0400 Received: from [199.232.76.173] (port=60117 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBacF-0001MJ-3r for qemu-devel@nongnu.org; Tue, 02 Jun 2009 16:29:47 -0400 Received: from mx2.redhat.com ([66.187.237.31]:33842) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MBacE-0003q6-CM for qemu-devel@nongnu.org; Tue, 02 Jun 2009 16:29:46 -0400 Message-ID: <4A258BB5.8060206@redhat.com> Date: Tue, 02 Jun 2009 23:29:41 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] remove pieces of source code References: <1243551838-1980-1-git-send-email-glommer@redhat.com> <4A1F77C0.9050407@codemonkey.ws> <4A1FA616.7040402@siemens.com> <4A1FA714.9030504@codemonkey.ws> <20090602200935.GA16182@miranda.arrow> In-Reply-To: <20090602200935.GA16182@miranda.arrow> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stuart Brady Cc: qemu-devel@nongnu.org Stuart Brady wrote: > Silly question, btw -- I've heard on several occasions that kqemu is not > auditable. Is it even possible to produce a replacement with reasonable > performance that *is* auditable? > Is it possible to produce a large scale system-level program (esp. with smp) that is auditable? I think not. kqemu is particularly difficult because it interacts with the hardware in complex ways. > (Whilst I certainly have the interest, I'm not sure whether I possess a > sufficient quantity of the other four required attributes to implement > something like this for KVM, if such a thing is even possible.) It's technically possible, but I don't think it's realistic. No one wants to code for yesterday's hardware; every day there are fewer machines that need kqemu. If you're interested in virtualization, but a cpu that supports virtualization. If you want to keep your old cpu, keep your old software as well. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.