All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nadav Har'El" <nyh@math.technion.ac.il>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add VMX cpuid feature to qemu64
Date: Wed, 5 Jan 2011 11:22:03 +0200	[thread overview]
Message-ID: <20110105092203.GA25003@fermat.math.technion.ac.il> (raw)
In-Reply-To: <4D243481.2070005@redhat.com>

On Wed, Jan 05, 2011, Avi Kivity wrote about "Re: [Qemu-devel] [PATCH] Add VMX cpuid feature to qemu64":
> IMO the emphasis on defaults is misplaced.  Most people run virtual 
> machines via a management tool, and we should focus on making it easy 
> for management tool maintainers to do the right thing, by documenting 
> our APIs and recommendations in the QEMU Management Tool Writer Guide.

Thanks. I'm withdrawing my patch, then, and will just keep the instruction
to use "-cpu host" in Nested VMX's README.

Just to add my last two cents on the subject, I think that from the same
assumption you make ("management tool maintainers will do the right thing")
I can draw an opposite conclusion: If qemu changes to use "kvm64" or "host"
by default, the management tool maintainers will any do the right thing by
explicitly stating the CPU type and not rely on the default, so nothing will
break. At the same time, people who do use the command line will benefit,
because they won't be baffled why the nested VMX feature, even if supported
by the KVM module, is hidden from them, while nested SVM isn't.

Thanks,
Nadav.

-- 
Nadav Har'El                        |    Wednesday, Jan  5 2011, 29 Tevet 5771
nyh@math.technion.ac.il             |-----------------------------------------
Phone +972-523-790466, ICQ 13349191 |Seen on a sign outside a church: "This is
http://nadav.harel.org.il           |a C H _ _ C H ... what's missing?"

      reply	other threads:[~2011-01-05  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 15:06 [Qemu-devel] [PATCH] Add VMX cpuid feature to qemu64 Nadav Har'El
2011-01-04 15:53 ` Alexander Graf
2011-01-04 21:39   ` Nadav Har'El
2011-01-04 21:55     ` Alexander Graf
2011-01-05  8:17       ` Nadav Har'El
2011-01-05  8:32         ` Avi Kivity
2011-01-05  8:50           ` Nadav Har'El
2011-01-05  9:06             ` Avi Kivity
2011-01-05  9:22               ` Nadav Har'El [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=20110105092203.GA25003@fermat.math.technion.ac.il \
    --to=nyh@math.technion.ac.il \
    --cc=agraf@suse.de \
    --cc=avi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.