From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Greg Kurz <groug@kaod.org>
Subject: Re: [Qemu-devel] [PATCH for 2.7] ppc: parse cpu features once
Date: Thu, 11 Aug 2016 08:46:06 +0530 [thread overview]
Message-ID: <20160811031606.GB4514@in.ibm.com> (raw)
In-Reply-To: <1470856081-28168-1-git-send-email-clg@kaod.org>
On Wed, Aug 10, 2016 at 09:08:01PM +0200, Cédric Le Goater wrote:
> From: Greg Kurz <groug@kaod.org>
>
> Considering that features are converted to global properties and
> global properties are automatically applied to every new instance
> of created CPU (at object_new() time), there is no point in
> parsing cpu_model string every time a CPU created. So move
> parsing outside CPU creation loop and do it only once.
>
> Parsing also should be done before any CPU is created so that
> features would affect the first CPU a well.
>
> This patch does that for all PowerPC machine types.
>
> It is based on previous work from Bharata:
>
> https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg07564.html
>
> Signed-off-by: Greg Kurz <groug@kaod.org>
> [clg: only kept the fix for the spapr platform. support for other
> platform will be added in 2.8 ]
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Tested-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
next prev parent reply other threads:[~2016-08-11 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 19:08 [Qemu-devel] [PATCH for 2.7] ppc: parse cpu features once Cédric Le Goater
2016-08-10 19:10 ` Cédric Le Goater
2016-08-11 3:16 ` Bharata B Rao [this message]
2016-08-11 7:14 ` David Gibson
2016-08-12 19:26 ` Eduardo Habkost
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=20160811031606.GB4514@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.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).