public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0 of 2] Remove --disable-cpu-emulation for qemu
Date: Wed, 18 Jun 2008 06:19:20 -0700	[thread overview]
Message-ID: <48590B58.4010005@qumranet.com> (raw)
In-Reply-To: <patchbomb.1213123834@thinkpadL>

Jerone Young wrote:
> These patches remove all traces of --disable-cpu-emulation configuration flag.
>
>   

I kind of like --disable-cpu-emulation.  It means we have the choice of 
kvm-only (low footprint, shuts up the security people), qemu-only 
(running cross-arch or on older cpu), and mixed mode (I'm a distro so  
don't know what cpu I'm running on).

Well, actually, at least Fedora already supplies both plain qemu and 
qemu-kvm, so it seems they don't care much about mixed mode.  I'll look 
at applying the patches.


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  parent reply	other threads:[~2008-06-18 13:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 18:50 [PATCH 0 of 2] Remove --disable-cpu-emulation for qemu Jerone Young
2008-06-10 18:50 ` [PATCH 1 of 2] Remove qemu files and entries associated with --disable-cpu-emulation configure argument Jerone Young
2008-06-10 18:50 ` [PATCH 2 of 2] Create dyngen dependency for exec.o for those who still have dyngen Jerone Young
2008-06-13 15:31 ` [PATCH 0 of 2] Remove --disable-cpu-emulation for qemu Jerone Young
2008-06-13 17:44   ` Anthony Liguori
2008-06-13 18:01     ` Soren Hansen
2008-06-13 22:13     ` Jerone Young
2008-06-17 13:27 ` Anthony Liguori
2008-06-18 13:19 ` Avi Kivity [this message]
2008-06-18 13:20   ` Avi Kivity
2008-06-18 20:56     ` Anthony Liguori

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=48590B58.4010005@qumranet.com \
    --to=avi@qumranet.com \
    --cc=jyoung5@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.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