From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-devel@nongnu.org,
agraf@suse.de, qemu-ppc@nongnu.org, abologna@redhat.com,
mdroth@linuc.vnet.ibm.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] target-ppc: Add POWER8E_v2.1 CPU model.
Date: Wed, 8 Jul 2015 17:02:45 +1000 [thread overview]
Message-ID: <559CCB15.3070806@ozlabs.ru> (raw)
In-Reply-To: <20150708064518.GO17857@voom.redhat.com>
On 07/08/2015 04:45 PM, David Gibson wrote:
> On Wed, Jul 08, 2015 at 04:40:27PM +1000, Alexey Kardashevskiy wrote:
>> On 07/08/2015 03:37 PM, David Gibson wrote:
>>> On Wed, Jul 08, 2015 at 02:10:28PM +1000, Alexey Kardashevskiy wrote:
>>>> On 07/08/2015 01:43 PM, David Gibson wrote:
>>>>> From: Andrea Bolognani <abologna@redhat.com>
>>>>>
>>>>> Add a missing PVR value for the POWER8E v2.1 CPU. Information taken
>>>> >from the kernel cputable.
>>>>>
>>>>> Signed-off-by: Andrea Bolognani <abologna@redhat.com>
>>>>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>>>>> ---
>>>>> target-ppc/cpu-models.c | 4 +++-
>>>>> target-ppc/cpu-models.h | 1 +
>>>>> 2 files changed, 4 insertions(+), 1 deletion(-)
>>>>>
>>>>> Alex,
>>>>>
>>>>> Not sure if this counts as a bugfix which can be merged now we're in
>>>>> the hard freeze. The lack of it does mean we can't work on one of our
>>>>> dev machines which has this CPU.
>>>>
>>>>
>>>> Why is this a stopper? We stopped bothering with exact PVRs some time ago
>>>> and -cpu POWER8 or -cpu host still work.
>>>
>>> Andrea, can you clarify?
>>>
>>> I think it's because libvirt likes to specify a specific CPU - and if
>>> it gets the new PVR from the host, qemu won't understand it.
>>
>>
>> A specific CPU in this case is "POWER8", I added this specifically for
>> libvirt (to allow migration between all versions of POWER8), it should not
>> use versioned CPUs and it does not in powerkvm.
>
> Uh.. won't that make qemu attempt to set a specific PVR, though -
> which will fail with recent KVM if it's not *exactly* the same as the
> host PVR.
The "POWER8" CPU class is created dynamically (like the "host" CPU class)
and has the actual host PVR so setting it to KVM cannot fail.
When TCG, the class is not registered and alias is used instead.
>> There is actually a patch to make this PVR masking/subclassing nicer, I
>> replied to it with adding you in cc:, please have a look. Andreas Faerber
>> had objections which I did not really grasp then.
>>
>>
>
--
Alexey
next prev parent reply other threads:[~2015-07-08 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 3:43 [Qemu-devel] [PATCH] target-ppc: Add POWER8E_v2.1 CPU model David Gibson
2015-07-08 4:10 ` Alexey Kardashevskiy
2015-07-08 5:37 ` David Gibson
2015-07-08 6:40 ` Alexey Kardashevskiy
2015-07-08 6:45 ` David Gibson
2015-07-08 7:02 ` Alexey Kardashevskiy [this message]
2015-07-08 16:35 ` Andrea Bolognani
2015-07-09 2:35 ` Alexey Kardashevskiy
2015-07-09 10:03 ` Andrea Bolognani
2015-07-10 5:19 ` Alexey Kardashevskiy
2015-07-10 9:19 ` Andrea Bolognani
2015-07-13 3:11 ` 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=559CCB15.3070806@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=abologna@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=mdroth@linuc.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).