From: "Andreas Färber" <afaerber@suse.de>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>, sPAPR <qemu-ppc@nongnu.org>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH for-next] spapr: Avoid "HOST@0" CPU node name in SLOF device tree for -cpu host
Date: Fri, 09 Aug 2013 13:34:15 +0200 [thread overview]
Message-ID: <5204D3B7.5060002@suse.de> (raw)
In-Reply-To: <52032980.9040900@linux.vnet.ibm.com>
Am 08.08.2013 07:15, schrieb Prerna Saxena:
> On 08/01/2013 06:32 AM, Andreas Färber wrote:
>> By default on KVM or when user asks for it via -cpu host, cpu_model will
>> be "host" and sPAPR merely upper-cases it for the SLOF device tree.
>>
>> Change it so that we get the underlying CPU type, e.g., "POWER7_V2.3@0".
>>
>> Reported-by: Prerna Saxena <prerna@linux.vnet.ibm.com>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>
> ACK.
> Reviewed and tested --Works as expected.
Thanks. Looking deeper into the issue I have come up with a simpler
solution that will obsolete this patch.
Andreas
>
> I'll send out an updated follow-up patch later in the day which ensures
> PAPR compliance for nomenclature.
>
> Regards,
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-08-09 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 1:02 [Qemu-devel] [PATCH for-next] spapr: Avoid "HOST@0" CPU node name in SLOF device tree for -cpu host Andreas Färber
2013-08-08 5:15 ` Prerna Saxena
2013-08-09 11:34 ` Andreas Färber [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=5204D3B7.5060002@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=anthony@codemonkey.ws \
--cc=prerna@linux.vnet.ibm.com \
--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 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.