qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Alexander Graf" <agraf@suse.de>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-ppc <qemu-ppc@nongnu.org>,
	qemu-stable@nongnu.org, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] Revert "target-ppc: Create versionless CPU class per family if KVM"
Date: Wed, 04 Mar 2015 09:14:10 +1100	[thread overview]
Message-ID: <54F63232.9090202@ozlabs.ru> (raw)
In-Reply-To: <54F61D09.2020601@suse.de>

On 03/04/2015 07:43 AM, Alexander Graf wrote:
>
>
> On 03.03.15 01:42, Alexey Kardashevskiy wrote:
>> On 03/03/2015 12:51 AM, Alexander Graf wrote:
>>>
>>>
>>> On 02.03.15 14:42, Andreas Färber wrote:
>>>> Am 02.03.2015 um 14:37 schrieb Alexander Graf:
>>>>> On 01.03.15 01:31, Andreas Färber wrote:
>>>>>> This reverts commit 5b79b1cadd3e565b6d1a5ba59764bd47af58b271 to avoid
>>>>>> double-registration of types:
>>>>>>
>>>>>>     Registering `POWER5+-powerpc64-cpu' which already exists
>>>>>>
>>>>>> Taking the textual description of a CPU type as part of a new type
>>>>>> name
>>>>>> is plain wrong, and so is unconditionally registering a new type here.
>>>>>>
>>>>>> Cc: Alexey Kardashevskiy <aik@ozlabs.ru>
>>>>>> Cc: qemu-stable@nongnu.org
>>>>>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>>>>>
>>>>> Doesn't this break p8 support?
>>>>
>>>> Maybe, but p5 support was in longer and this is definitely a regression
>>>> and really really wrong. If you know a way to fix it without handing it
>>>> back to the IBM guys for more thought, feel free to give it a shot.
>>>
>>> I honestly don't fully remember what this was about. Wasn't this our
>>> special KVM class that we use to create a compatible cpu type on the fly?
>>>
>>> Alexey, please take a look at it.
>>
>>
>> I sent a note yesterday :-/ Here it is again:
>>
>> With this revert, running qemu with HV KVM and -cpu POWER7 fails on real
>> POWER7 machine as my machine has pvr 003f 0201 and POWER7 is an alias of
>> POWER7_v2.3 (pvr 003f 0203); and this is what I tried to fix at the
>> first place. QEMU looks at classes first, and if not found - at aliases,
>> so this worked.
>>
>> I would rename "POWER5+" to "POWER5+_0.0" and make "POWER5+" an alias
>> for POWER5+_v2.1 (or POWER5+_0.0).
>
> Care to send a patch?

I wonder if Andreas has a better solution to my initial problem - he 
obviously won't like the proposed patch :)




-- 
Alexey

  reply	other threads:[~2015-03-03 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01  0:31 [Qemu-devel] [PATCH] Revert "target-ppc: Create versionless CPU class per family if KVM" Andreas Färber
     [not found] ` <54F4678D.20909@suse.de>
2015-03-02 13:42   ` Andreas Färber
2015-03-02 13:51     ` Alexander Graf
2015-03-02 14:07       ` Andreas Färber
2015-03-03  0:42       ` Alexey Kardashevskiy
2015-03-03 20:43         ` Alexander Graf
2015-03-03 22:14           ` Alexey Kardashevskiy [this message]
2015-03-04 14:55             ` Andreas Färber
2015-03-04 23:50               ` Alexey Kardashevskiy

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=54F63232.9090202@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-stable@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).