qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Stuart Brady <sdbrady@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] remove pieces of source code
Date: Tue, 02 Jun 2009 23:29:41 +0300	[thread overview]
Message-ID: <4A258BB5.8060206@redhat.com> (raw)
In-Reply-To: <20090602200935.GA16182@miranda.arrow>

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.

  reply	other threads:[~2009-06-02 20:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 23:03 [Qemu-devel] [PATCH] remove pieces of source code Glauber Costa
2009-05-29  5:50 ` Anthony Liguori
2009-05-29  9:08   ` [Qemu-devel] " Jan Kiszka
2009-05-29  9:12     ` Anthony Liguori
2009-05-29  9:35       ` Stefan Weil
2009-06-02 20:09       ` Stuart Brady
2009-06-02 20:29         ` Avi Kivity [this message]
2009-05-29 10:00     ` Daniel P. Berrange
2009-05-29 10:20       ` Jan Kiszka
2009-05-29 11:35     ` Glauber Costa
2009-05-30 18:04     ` François Revol
2009-05-31  9:13       ` Jan Kiszka
2009-05-31 14:53     ` Jamie Lokier
2009-05-31 15:43       ` Jan Kiszka
2009-05-29 11:32   ` [Qemu-devel] " Glauber Costa
2009-05-29 11:42     ` Gerd Hoffmann
2009-05-29 15:43     ` [Qemu-devel] " Consul
2009-05-29 18:49       ` Glauber Costa
2009-05-30 10:26         ` Andreas Färber
2009-05-31  9:15           ` Jan Kiszka
2009-05-31 13:08             ` Andreas Färber
2009-05-31 13:40               ` Avi Kivity
2009-05-31 16:20                 ` M. Warner Losh
2009-05-31 15:10               ` Jan Kiszka
2009-06-06 10:17                 ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A258BB5.8060206@redhat.com \
    --to=avi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sdbrady@ntlworld.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).