From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: clg@kaod.org, 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:32:43 +0200 [thread overview]
Message-ID: <20161028113243.0a4e92d4@bahia> (raw)
In-Reply-To: <1477620301-24822-1-git-send-email-david@gibson.dropbear.id.au>
On Fri, 28 Oct 2016 13:05:01 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> powernv has some code (derived from the spapr equivalent) used in device
> tree generation which depends on the CPU's compatibility mode / logical
> PVR. However, compatibility modes don't make sense on powernv - at least
> not as a property controlled by the host - because the guest in powernv
> has full hypervisor level access to the virtual system, and so owns the
> PCR (Processor Compatibility Register) which implements compatiblity modes.
>
This makes a lot of sense indeed.
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> hw/ppc/pnv.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> Hi Cédric, I'd appreciate it if you can double check my reasoning
> here. This patch gets powernv out of the way of a bunch of
> compatibility mode cleanups I have in the works.
>
> 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;
Not speaking of the PCR, this has also another effect since
ppc_get_compat_smt_threads() also take the KVM smt capability
into account:
int ret = MIN(cs->nr_threads, kvmppc_smt_threads());
Shouldn't you do the same here ?
> 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 9:32 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 [this message]
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
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=20161028113243.0a4e92d4@bahia \
--to=groug@kaod.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.