qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Luc Michel <luc.michel@greensocs.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Alistair Francis" <alistair@alistair23.me>,
	"Mark Burton" <mark.burton@greensocs.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Sai Pavan Boddu" <saipava@xilinx.com>,
	"Edgar Iglesias" <edgari@xilinx.com>,
	qemu-arm <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v7 01/16] hw/cpu: introduce CPU clusters
Date: Mon, 3 Dec 2018 11:23:56 +0000	[thread overview]
Message-ID: <CAFEAcA8j4xTiS3_ktiA0hm2N4cu5RvxAtYqUHgvY-bUXgcwbjQ@mail.gmail.com> (raw)
In-Reply-To: <b8e20686-e5d1-a844-48f7-a4ae471e3fd5@greensocs.com>

On Mon, 3 Dec 2018 at 11:21, Luc Michel <luc.michel@greensocs.com> wrote:
>
> On 11/30/18 5:52 PM, Peter Maydell wrote:
> > Luc: what are the requirements on boards using CPU cluster
> > objects? I assume these are both OK:
> >  * does not use cluster objects at all
> >    (the gdbstub puts all the CPUs in one process?)
> Yes, when no clusters are found, a process with PID 1 is created and
> used for all CPUs.
> >  * all CPUs created are in some CPU cluster
> >    (the gdbstub uses one process per CPU cluster)
> > but what about
> >  * some CPUs are created in a CPU cluster, but some
> >    are "loose", not in any cluster at all> ?
> > Is that just invalid, or do the "loose" CPUs end up in
> > a default cluster (gdbstub process), or do they get
> > one cluster each?
> Currently this is valid and the "loose" CPUs end up in the first
> available process (which will be PID 1 if we are in your first case,
> i.e. no clusters in the machine).

So if there are some defined clusters 1 and 2, and some
loose CPUs, the clusters get PID 1 and PID 2, and the
loose CPUs end up in PID 3? That seems reasonable.

thanks
-- PMM

  reply	other threads:[~2018-12-03 11:24 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23  9:17 [Qemu-devel] [PATCH v7 00/16] gdbstub: support for the multiprocess extension Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 01/16] hw/cpu: introduce CPU clusters Luc Michel
2018-11-23 18:10   ` Eduardo Habkost
2018-11-23 18:14     ` Peter Maydell
2018-11-23 18:24       ` Eduardo Habkost
2018-11-23 18:53         ` Peter Maydell
2018-11-23 22:38           ` Eduardo Habkost
2018-11-25 21:27     ` Philippe Mathieu-Daudé
2018-11-26 13:27       ` Eduardo Habkost
2018-11-30 16:52         ` Peter Maydell
2018-11-30 18:14           ` Eduardo Habkost
2018-12-03 11:20           ` Luc Michel
2018-12-03 11:23             ` Peter Maydell [this message]
2018-12-03 14:09               ` Luc Michel
2018-12-04 18:06                 ` Eduardo Habkost
2018-12-04 18:24                   ` Peter Maydell
2018-12-04 19:05                     ` Eduardo Habkost
2018-12-04 19:16                       ` Peter Maydell
2018-12-04 19:45                         ` Eduardo Habkost
2018-12-05 14:02                           ` Luc Michel
2018-12-05 16:47                             ` Eduardo Habkost
2018-12-05 13:44                     ` Luc Michel
2018-12-05 13:47                   ` Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 02/16] gdbstub: introduce GDB processes Luc Michel
2018-11-25 20:58   ` Philippe Mathieu-Daudé
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 03/16] gdbstub: add multiprocess support to '?' packets Luc Michel
2018-11-25 21:22   ` Philippe Mathieu-Daudé
2018-12-06 12:27     ` Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 04/16] gdbstub: add multiprocess support to 'H' and 'T' packets Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 05/16] gdbstub: add multiprocess support to vCont packets Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 06/16] gdbstub: add multiprocess support to 'sC' packets Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 07/16] gdbstub: add multiprocess support to (f|s)ThreadInfo and ThreadExtraInfo Luc Michel
2018-11-30 10:35   ` Edgar E. Iglesias
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 08/16] gdbstub: add multiprocess support to Xfer:features:read: Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 09/16] gdbstub: add multiprocess support to gdb_vm_state_change() Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 10/16] gdbstub: add multiprocess support to 'D' packets Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 11/16] gdbstub: add support for extended mode packet Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 12/16] gdbstub: add support for vAttach packets Luc Michel
2018-11-25 21:00   ` Philippe Mathieu-Daudé
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 13/16] gdbstub: processes initialization on new peer connection Luc Michel
2018-11-25 21:02   ` Philippe Mathieu-Daudé
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 14/16] gdbstub: gdb_set_stop_cpu: ignore request when process is not attached Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 15/16] gdbstub: add multiprocess extension support Luc Michel
2018-11-23  9:17 ` [Qemu-devel] [PATCH v7 16/16] arm/xlnx-zynqmp: put APUs and RPUs in separate CPU clusters Luc Michel
2018-11-25 21:10   ` Philippe Mathieu-Daudé

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=CAFEAcA8j4xTiS3_ktiA0hm2N4cu5RvxAtYqUHgvY-bUXgcwbjQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alistair@alistair23.me \
    --cc=edgari@xilinx.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=luc.michel@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=saipava@xilinx.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).