From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] powernv: CPU compatibility modes don't make sense for powernv
Date: Fri, 28 Oct 2016 11:46:03 -0500 [thread overview]
Message-ID: <1477673163.32311.39.camel@kernel.crashing.org> (raw)
In-Reply-To: <b006dfb9-1a6d-3b5c-ca9e-e9b6cede8449@kaod.org>
On Fri, 2016-10-28 at 18:40 +0200, Cédric Le Goater wrote:
>
> It makes perfect sense. The "cpu-version" property is for PAPR, not
> for OPAL.
> hostboot and skiboot put SPR_PVR in this property.
>
> I will be careful using 'CPU_CORE(pc)->nr_threads' in the ICP patches
> also.
No, the cpu-version is part of the old OF bindings afaik, at least it
exists under OPAL, so it should be there but yes, it should just
contain the PVR.
Cheers,
Ben.
> Reviewed-by: Cédric Le Goater <clg@kaod.org>
>
> Thanks,
>
> C.
>
>
> >
> >
> > diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> > index 82276e0..6af3424 100644
> > --- a/hw/ppc/pnv.c
> > +++ b/hw/ppc/pnv.c
> > @@ -110,7 +110,7 @@ static void powernv_create_core_node(PnvChip
> > *chip, PnvCore *pc, void *fdt)
> > CPUState *cs = CPU(DEVICE(pc->threads));
> > DeviceClass *dc = DEVICE_GET_CLASS(cs);
> > PowerPCCPU *cpu = POWERPC_CPU(cs);
> > - int smt_threads = ppc_get_compat_smt_threads(cpu);
> > + int smt_threads = CPU_CORE(pc)->nr_threads;
> > CPUPPCState *env = &cpu->env;
> > PowerPCCPUClass *pcc = POWERPC_CPU_GET_CLASS(cs);
> > uint32_t servers_prop[smt_threads];
> > @@ -206,10 +206,6 @@ static void powernv_create_core_node(PnvChip
> > *chip, PnvCore *pc, void *fdt)
> > _FDT((fdt_setprop(fdt, offset, "ibm,pa-features",
> > pa_features, sizeof(pa_features))));
> >
> > - if (cpu->cpu_version) {
> > - _FDT((fdt_setprop_cell(fdt, offset, "cpu-version", cpu-
> > >cpu_version)));
> > - }
> > -
> > /* Build interrupt servers properties */
> > for (i = 0; i < smt_threads; i++) {
> > servers_prop[i] = cpu_to_be32(pc->pir + i);
> >
next prev parent reply other threads:[~2016-10-28 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 2:05 [Qemu-devel] [RFC] powernv: CPU compatibility modes don't make sense for powernv David Gibson
2016-10-28 9:32 ` Greg Kurz
2016-10-28 11:14 ` David Gibson
2016-10-28 13:23 ` Greg Kurz
2016-10-28 16:40 ` Cédric Le Goater
2016-10-28 16:46 ` Benjamin Herrenschmidt [this message]
2016-10-28 16:51 ` Cédric Le Goater
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=1477673163.32311.39.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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.