From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: paulus@ozlabs.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [QEMU-PPC] [PATCH] target/ppc: Add ibm, purr and ibm, spurr device-tree properties
Date: Tue, 07 May 2019 09:43:34 +1000 [thread overview]
Message-ID: <1557186214.6435.2.camel@gmail.com> (raw)
In-Reply-To: <20190506032304.GB6790@umbus.fritz.box>
On Mon, 2019-05-06 at 13:23 +1000, David Gibson wrote:
> On Mon, May 06, 2019 at 11:48:03AM +1000, Suraj Jitindar Singh wrote:
> > The ibm,purr and ibm,spurr device tree properties are used to
> > indicate
> > that the processor implements the Processor Utilisation of
> > Resources
> > Register (PURR) and Scaled Processor Utilisation of Resources
> > Registers
> > (SPURR), respectively. Each property has a single value which
> > represents
> > the level of architecture supported. A value of 1 for ibm,purr
> > means
> > support for the version of the PURR defined in book 3 in version
> > 2.02 of
> > the architecture. A value of 1 for ibm,spurr means support for the
> > version of the SPURR defined in version 2.05 of the architecture.
> >
> > Add these properties for all processors for which the PURR and
> > SPURR
> > registers are generated.
>
> So.. what does the current empty property mean? Is it just wrong by
> spec, or does it actually mean something incorrect?
Af far as I can tell, an empty property is invalid according to PAPR.
A level value is required to communicate the level of purr implemented.
Should probably have:
Fixes: 0da6f3fef9a "spapr: Reorganize CPU dt generation code"
>
> >
> > Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
> > ---
> > hw/ppc/spapr.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> > index 2ef3ce4362..8580a8dc67 100644
> > --- a/hw/ppc/spapr.c
> > +++ b/hw/ppc/spapr.c
> > @@ -500,7 +500,10 @@ static void spapr_populate_cpu_dt(CPUState
> > *cs, void *fdt, int offset,
> > _FDT((fdt_setprop(fdt, offset, "64-bit", NULL, 0)));
> >
> > if (env->spr_cb[SPR_PURR].oea_read) {
> > - _FDT((fdt_setprop(fdt, offset, "ibm,purr", NULL, 0)));
> > + _FDT((fdt_setprop_cell(fdt, offset, "ibm,purr", 1)));
> > + }
> > + if (env->spr_cb[SPR_SPURR].oea_read) {
> > + _FDT((fdt_setprop_cell(fdt, offset, "ibm,spurr", 1)));
> > }
> >
> > if (ppc_hash64_has(cpu, PPC_HASH64_1TSEG)) {
>
>
next prev parent reply other threads:[~2019-05-06 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 1:48 [Qemu-devel] [QEMU-PPC] [PATCH] target/ppc: Add ibm, purr and ibm, spurr device-tree properties Suraj Jitindar Singh
2019-05-06 3:23 ` David Gibson
2019-05-06 23:43 ` Suraj Jitindar Singh [this message]
2019-05-07 5:16 ` David Gibson
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=1557186214.6435.2.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@ozlabs.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 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.