From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] merging kqemu into mainline kernel?
Date: Thu, 16 Aug 2007 15:31:51 +0100 [thread overview]
Message-ID: <200708161531.52249.paul@codesourcery.com> (raw)
In-Reply-To: <779506c70708160702v52d1305u8d513b1dc9a81c98@mail.gmail.com>
> > Mainly because the kernel already has one perfectly good virtualization
> > interface. There's very little motivation to add another incompatible
> > one, especially when the implementation is known to be fundamentally
> > flawed, and probably insecure.
> >
> > If you really want to get it merged I suggest modifying kqemu to use the
> > kvm interface, augmenting the kvm interface if necessary.
>
> Are you referring to the API when you say interface, or the
> functionality itself? If the former that's a reasonable argument, but
> the latter is not valid since KVM requires a VT or AMD-V-capable
> processor, right? KQEMU does not, and therefore [today] works on a
> much larger installed base of hardware.
Yes, I mean the API. However in practice you'd probably want to try and share
the implementation as well. In short it's likely to need rewriting before
it's acceptable upstream.
Paul
P.S. Please don't top-post. Consider this your final warning.
next prev parent reply other threads:[~2007-08-16 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 15:16 [Qemu-devel] merging kqemu into mainline kernel? dragoran
2007-08-04 16:26 ` Ricardo Almeida
2007-08-04 17:04 ` dragoran
2007-08-16 12:42 ` Bill C. Riemers
2007-08-16 12:53 ` dragoran
2007-08-16 13:49 ` Paul Brook
2007-08-16 14:02 ` Leonardo Reiter
2007-08-16 14:31 ` Paul Brook [this message]
2007-08-16 19:05 ` Christian MICHON
2007-08-16 19:51 ` Ed Swierk
2007-08-16 15:01 ` Jernej Simonèiè
2007-08-16 15:13 ` Daniel P. Berrange
2007-08-16 15:15 ` Luke -Jr
2007-08-16 15:00 ` Bill C. Riemers
2007-08-17 12:44 ` dragoran
2007-08-17 13:19 ` Sunil Amitkumar Janki
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=200708161531.52249.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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).