All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Peter Crosthwaite <crosthwaite.peter@gmail.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	Cedric Le Goater <clg@kaod.org>,
	bharata@linux.vnet.ibm.com, Scott Wood <scottwood@freescale.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/8] ppc: compute cpu_dt_id in the machine code
Date: Wed, 29 Jun 2016 23:07:12 +0200	[thread overview]
Message-ID: <20160629230712.69db03ea@bahia.lan> (raw)
In-Reply-To: <146723340662.9665.6413150884317978000.stgit@bahia.lan>

On Wed, 29 Jun 2016 22:50:06 +0200
Greg Kurz <groug@kaod.org> wrote:

> This series is a sequel to the discussion on a patch from Ben's powernv
> patchset:
> 
>         http://patchwork.ozlabs.org/patch/597153/
> 
> Indeed, since the DT is a machine abstraction, it should definitely sit
> under hw/ppc and not in the target code:
> - all machine types are forced to share the same numbering logic
> - user mode does not need that => there are #ifdef everywhere
> 
> So this series moves all the current numbering logic to the machine
> code. It also provides the ability for each machine type to provide
> its own numbering logic instead of using the legacy one.
> 
> The current code computes cpu_dt_id out of cpu_index, both getting
> their values during cpu realization.
> 
> The idea is to compute cpu_index at cpu initialization time, so
> that the machine can compute cpu_dt_id before realizing the cpu.
> 
> I had to fix some issues and to do some more structural changes to have
> this working, hence the RFC tag. The first 4 patches are bug fixes. The
> next ones do what the subject says.
> 

Of course I forgot to add the RFC tag in the subject :) but yes, the 4
last patches especially deserve some feedback and are definitely not
2.7 material.

> This patchset is based on David's ppc-for-2.7 branch. I could test it plays
> nicely with Bharata's CPU hotplug code for sPAPR.
> 
> There are some more places where the cpu_dt_id logic is open coded in the
> sPAPR code. It may be worth to consolidate that in follow-up patches. Also
> maybe other machine types may provide their own numbering logic if the
> current one is not appropriate.
> 
> Please comment.
> 
> ---
> 
> Greg Kurz (8):
>       spapr: drop reference on child object during core realization
>       spapr: do proper error propagation in spapr_cpu_core_realize_child()
>       spapr: drop duplicate variable in spapr_core_release()
>       exec: add missing conditional compilation
>       exec: move cpu_index init and exit to their own function
>       ppc: move cpu index setup to instance_init/finalize
>       cpu: add initialization helper without realize
>       hw/ppc: move DT cpu id generation to machine code
> 
> 
>  exec.c                      |   72 +++++++++++++++++++++++++++++++++----------
>  hw/ppc/e500.c               |    2 +
>  hw/ppc/mac_newworld.c       |    2 +
>  hw/ppc/mac_oldworld.c       |    2 +
>  hw/ppc/ppc.c                |   60 ++++++++++++++++++++++++++++++++++++
>  hw/ppc/ppc440_bamboo.c      |    2 +
>  hw/ppc/ppc4xx_devs.c        |    2 +
>  hw/ppc/prep.c               |    2 +
>  hw/ppc/spapr.c              |    2 +
>  hw/ppc/spapr_cpu_core.c     |   23 ++++++++++----
>  hw/ppc/virtex_ml507.c       |    2 +
>  include/exec/exec-all.h     |    2 +
>  include/hw/ppc/ppc.h        |    4 ++
>  include/qom/cpu.h           |   14 ++++++++
>  qom/cpu.c                   |   19 ++++++++++-
>  target-ppc/translate_init.c |   42 ++++++-------------------
>  16 files changed, 185 insertions(+), 67 deletions(-)
> 
> --
> Greg
> 
> 

  parent reply	other threads:[~2016-06-29 21:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 20:50 [Qemu-devel] [PATCH 0/8] ppc: compute cpu_dt_id in the machine code Greg Kurz
2016-06-29 20:50 ` [Qemu-devel] [PATCH 1/8] spapr: drop reference on child object during core realization Greg Kurz
2016-06-30  4:27   ` Bharata B Rao
2016-06-29 20:50 ` [Qemu-devel] [PATCH 2/8] spapr: do proper error propagation in spapr_cpu_core_realize_child() Greg Kurz
2016-06-30  4:28   ` Bharata B Rao
2016-06-29 20:50 ` [Qemu-devel] [PATCH 3/8] spapr: drop duplicate variable in spapr_core_release() Greg Kurz
2016-06-30  4:29   ` Bharata B Rao
2016-06-29 20:50 ` [Qemu-devel] [PATCH 4/8] exec: add missing conditional compilation Greg Kurz
2016-06-29 20:51 ` [Qemu-devel] [PATCH 5/8] exec: move cpu_index init and exit to their own function Greg Kurz
2016-06-29 20:51 ` [Qemu-devel] [PATCH 6/8] ppc: move cpu index setup to instance_init/finalize Greg Kurz
2016-06-29 20:51 ` [Qemu-devel] [PATCH 7/8] cpu: add initialization helper without realize Greg Kurz
2016-06-29 20:51 ` [Qemu-devel] [PATCH 8/8] hw/ppc: move DT cpu id generation to machine code Greg Kurz
2016-06-29 21:07 ` Greg Kurz [this message]
2016-06-30  5:07 ` [Qemu-devel] [PATCH 0/8] ppc: compute cpu_dt_id in the " David Gibson
2016-06-30  7:34 ` Igor Mammedov
2016-06-30  9:43   ` Greg Kurz

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=20160629230712.69db03ea@bahia.lan \
    --to=groug@kaod.org \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=clg@kaod.org \
    --cc=crosthwaite.peter@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=scottwood@freescale.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 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.