From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] Unbreak large mem support by removing kqemu
Date: Thu, 13 Aug 2009 13:13:47 +0100 [thread overview]
Message-ID: <200908131313.47711.paul@codesourcery.com> (raw)
In-Reply-To: <1249942586-12671-1-git-send-email-aliguori@us.ibm.com>
> kqemu introduces a number of restrictions on the i386 target.
> kvm is a viable alternative for people looking to accelerate qemu and has
> the benefit of being supported by the upstream Linux kernel. If someone
> can implement work arounds to remove the restrictions introduced by kqemu,
> I'm happy to avoid and/or revert this patch.
> Paul, please Ack or Nack this patch.
Ok.
I think we've kept kqemu lying around in a semi-broken state long enough that
we can demonstrate lack of active developer interest. Anyone that really cares
can always retrieve it from git history and start from there.
Paul
prev parent reply other threads:[~2009-08-13 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 22:16 [Qemu-devel] [PATCH 1/2] Unbreak large mem support by removing kqemu Anthony Liguori
2009-08-10 22:16 ` [Qemu-devel] [PATCH 2/2] Only build osdep once Anthony Liguori
2009-08-13 12:13 ` Paul Brook [this message]
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=200908131313.47711.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.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).