From: "Ricardo Almeida" <ric.almeida@gmail.com>
To: qemu-devel@nongnu.org, dragoran <drago01@gmail.com>
Subject: Re: [Qemu-devel] merging kqemu into mainline kernel?
Date: Sat, 4 Aug 2007 17:26:30 +0100 [thread overview]
Message-ID: <8a6cde920708040926s6e12edd0mc3b469ab741c5653@mail.gmail.com> (raw)
In-Reply-To: <f6ca9fed0708030816o769586b9ie67fa1fa86644cdb@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi,
I'm just a user...
Is it planned to submit kqemu to lkml for inclusion into the mainline
> kernel?
Never seen anyone talking about this...
if not why?
Maybe because KVM was included (
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7)
if yes any idea when? is it possible to try to get it in 2.6.24 ?
>
I don't know if Linus would accept it. As I said, KVM was included, although
kqemu as the advantage of working in older hardware (without AMD-V or Intel
equivalent virtualization instructions).
Maybe if it was possible to make merge kqemu into KVM to take the best of
the two... But I don't know anything about KVM nor kqemu code...
Regards,
Ricardo Almeida
[-- Attachment #2: Type: text/html, Size: 1423 bytes --]
next prev parent reply other threads:[~2007-08-04 16:27 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 [this message]
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
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=8a6cde920708040926s6e12edd0mc3b469ab741c5653@mail.gmail.com \
--to=ric.almeida@gmail.com \
--cc=drago01@gmail.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).