qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-ppc <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] RFC: powerpc: add PVR compatibility check
Date: Tue, 05 Nov 2013 17:16:33 +0100	[thread overview]
Message-ID: <527919E1.1000902@suse.de> (raw)
In-Reply-To: <7403BE51-422E-4987-A20F-F22655829ECC@suse.de>

Am 05.11.2013 07:05, schrieb Alexander Graf:
> 
> 
> Am 05.11.2013 um 05:00 schrieb Paul Mackerras <paulus@samba.org>:
> 
>> On Mon, Nov 04, 2013 at 10:05:58AM +0100, Alexander Graf wrote:
>>>
>>> Yeah, we really need to check that guest vpcu == host vcpu for HV KVM.
>>
>> In general I agree, but the one difficulty I see is that a check for
>> exact equality will interact badly with qemu's habit of picking a
>> specific processor version when the user specifies something general
>> like "POWER7".  So if the user does -cpu POWER7 on a machine with
>> (for example) a POWER7 v2.1 processor, but qemu arbitrarily picks the
>> PVR for POWER7 v2.3, then it will fail, which will be completely
>> puzzling to the user -- "I asked for POWER7, and it is a POWER7,
>> what's the problem??".
>>
>> Maybe if the user asks for a non-specific processor type, and the
>> host's PVR matches the request, then qemu should take the host's PVR
>> rather than just picking some arbitrary processor version.
> 
> Yup.

But then it's no longer generally reproducible: "POWER7" won't be
"POWER7" on another machine.

One thing I original did iirc was to hide the aliases from QMP. You can
always do stupid things on the command line and then we can blame you,
but if libvirt and upper layers don't offer "POWER7" to the end user
then we don't need to worry about the average user misinterpreting its
semantics.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-11-05 16:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  3:36 [Qemu-devel] [PATCH] RFC: powerpc: add PVR compatibility check Alexey Kardashevskiy
2013-11-04  7:47 ` Alexander Graf
2013-11-04  8:58   ` Alexey Kardashevskiy
2013-11-04  9:05     ` Alexander Graf
2013-11-04  9:24       ` Alexey Kardashevskiy
2013-11-04  9:29         ` Alexander Graf
2013-11-05  4:00       ` Paul Mackerras
2013-11-05  6:05         ` Alexander Graf
2013-11-05 16:16           ` Andreas Färber [this message]
2013-11-05 16:18             ` Alexander Graf
2013-11-06  3:02             ` Paul Mackerras
2013-11-06 12:19               ` Alexander Graf

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=527919E1.1000902@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=anthony@codemonkey.ws \
    --cc=paulus@samba.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).