From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] target/ppc: Avoid printing wrong aliases in CPU help text
Date: Tue, 9 May 2017 17:11:19 +1000 [thread overview]
Message-ID: <20170509071119.GP25748@umbus.fritz.box> (raw)
In-Reply-To: <a44802fe-780c-8a5d-ba1d-a9969748f19d@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4758 bytes --]
On Tue, May 09, 2017 at 06:49:29AM +0200, Thomas Huth wrote:
> On 08.03.2017 20:05, Thomas Huth wrote:
> > When running with KVM, we update the "family" CPU alias to point
> > to the right host CPU type, so that it is for example possible to
> > use "-cpu POWER8" on a POWER8NVL host. However, the function for
> > printing the list of available CPU models is called earlier than
> > the KVM setup code, so the output of "-cpu help" is wrong in that
> > case. Since it would be somewhat ugly anyway to have different
> > help texts depending on whether "-enable-kvm" has been specified
> > or not, we should better always print the same text, so fix this
> > issue by printing "alias for preferred XXX CPU" instead.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > target/ppc/cpu.h | 1 +
> > target/ppc/kvm.c | 12 ------------
> > target/ppc/translate_init.c | 27 +++++++++++++++++++++++++--
> > 3 files changed, 26 insertions(+), 14 deletions(-)
> >
> > diff --git a/target/ppc/cpu.h b/target/ppc/cpu.h
> > index 7c4a1f5..21752ff 100644
> > --- a/target/ppc/cpu.h
> > +++ b/target/ppc/cpu.h
> > @@ -1216,6 +1216,7 @@ static inline PowerPCCPU *ppc_env_get_cpu(CPUPPCState *env)
> >
> > PowerPCCPUClass *ppc_cpu_class_by_pvr(uint32_t pvr);
> > PowerPCCPUClass *ppc_cpu_class_by_pvr_mask(uint32_t pvr);
> > +PowerPCCPUClass *ppc_cpu_get_family_class(PowerPCCPUClass *pcc);
> >
> > struct PPCVirtualHypervisor {
> > Object parent;
> > diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
> > index 9f1f132..585e6d3 100644
> > --- a/target/ppc/kvm.c
> > +++ b/target/ppc/kvm.c
> > @@ -2304,18 +2304,6 @@ bool kvmppc_has_cap_htm(void)
> > return cap_htm;
> > }
> >
> > -static PowerPCCPUClass *ppc_cpu_get_family_class(PowerPCCPUClass *pcc)
> > -{
> > - ObjectClass *oc = OBJECT_CLASS(pcc);
> > -
> > - while (oc && !object_class_is_abstract(oc)) {
> > - oc = object_class_get_parent(oc);
> > - }
> > - assert(oc);
> > -
> > - return POWERPC_CPU_CLASS(oc);
> > -}
> > -
> > PowerPCCPUClass *kvm_ppc_get_host_cpu_class(void)
> > {
> > uint32_t host_pvr = mfpvr();
> > diff --git a/target/ppc/translate_init.c b/target/ppc/translate_init.c
> > index c1a9014..9e9c37f 100644
> > --- a/target/ppc/translate_init.c
> > +++ b/target/ppc/translate_init.c
> > @@ -10249,6 +10249,18 @@ PowerPCCPU *cpu_ppc_init(const char *cpu_model)
> > return POWERPC_CPU(cpu_generic_init(TYPE_POWERPC_CPU, cpu_model));
> > }
> >
> > +PowerPCCPUClass *ppc_cpu_get_family_class(PowerPCCPUClass *pcc)
> > +{
> > + ObjectClass *oc = OBJECT_CLASS(pcc);
> > +
> > + while (oc && !object_class_is_abstract(oc)) {
> > + oc = object_class_get_parent(oc);
> > + }
> > + assert(oc);
> > +
> > + return POWERPC_CPU_CLASS(oc);
> > +}
> > +
> > /* Sort by PVR, ordering special case "host" last. */
> > static gint ppc_cpu_list_compare(gconstpointer a, gconstpointer b)
> > {
> > @@ -10280,6 +10292,7 @@ static void ppc_cpu_list_entry(gpointer data, gpointer user_data)
> > ObjectClass *oc = data;
> > CPUListState *s = user_data;
> > PowerPCCPUClass *pcc = POWERPC_CPU_CLASS(oc);
> > + DeviceClass *family = DEVICE_CLASS(ppc_cpu_get_family_class(pcc));
> > const char *typename = object_class_get_name(oc);
> > char *name;
> > int i;
> > @@ -10302,8 +10315,18 @@ static void ppc_cpu_list_entry(gpointer data, gpointer user_data)
> > if (alias_oc != oc) {
> > continue;
> > }
> > - (*s->cpu_fprintf)(s->file, "PowerPC %-16s (alias for %s)\n",
> > - alias->alias, name);
> > + /*
> > + * If running with KVM, we might update the family alias later, so
> > + * avoid printing the wrong alias here and use "preferred" instead
> > + */
> > + if (strcmp(alias->alias, family->desc) == 0) {
> > + (*s->cpu_fprintf)(s->file,
> > + "PowerPC %-16s (alias for preferred %s CPU)\n",
> > + alias->alias, family->desc);
> > + } else {
> > + (*s->cpu_fprintf)(s->file, "PowerPC %-16s (alias for %s)\n",
> > + alias->alias, name);
> > + }
> > }
> > g_free(name);
> > }
> >
>
> Ping!
>
> ... I think this got somehow lost in the 2.9 rush ...
Yes, I think so. Can you make sure it's rebased and repost, please.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-05-10 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 19:05 [Qemu-devel] [PATCH] target/ppc: Avoid printing wrong aliases in CPU help text Thomas Huth
2017-03-08 20:03 ` Eduardo Habkost
2017-05-09 4:49 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2017-05-09 7:11 ` David Gibson [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=20170509071119.GP25748@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.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).