qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: shlomo.pongratz@toganetworks.com
Cc: Shlomo Pongratz <shlomo.pongratz@huawei.com>,
	Claudio Fontana <claudio.fontana@huawei.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH RFC] Implement GIC-500 from GICv3 family for arm64
Date: Tue, 10 Mar 2015 00:13:26 +0900	[thread overview]
Message-ID: <CAFEAcA8zkno-jJEkV2RCWeSX1swiYaLgOcJVSF1PFP-Ww6pCEA@mail.gmail.com> (raw)
In-Reply-To: <1425912119-15681-1-git-send-email-shlomo.pongratz@toganetworks.com>

On 9 March 2015 at 23:41,  <shlomo.pongratz@toganetworks.com> wrote:
> From: Shlomo Pongratz <shlomo.pongratz@huawei.com>
>
> This patch is a first step toward 128 cores support for arm64.
>
> At first only 64 cores are supported for two reasons:
> First the largest integer type has the size of 64 bits and modifying
> essential data structures in order to support 128 cores will require
> the usage of bitops.
> Second currently the Linux (kernel) can be configured to support
> up to 64 cores thus there is no urgency with 128 cores support.
>
> Things left to do:
>
> Currently the booting Linux may got stuck. The probability of getting stuck
> increases with the number of cores. I'll appreciate core review.
>
> There is a need to support flexible clusters size. The GIC-500 can support
> up to 128 cores, up to 32 clusters and up to 8 cores is a cluster.
> So for example, if one wishes to have 16 cores, the options are:
> 2 clusters of 8 cores each, 4 clusters with 4 cores each
> Currently only the first option is supported.
> There is an issue of passing clock affinity to via the dtb. In the dtb
>
> interrupt section there are only 24 bit left to affinity since the
> variable is a 32 bit entity and 8 bits are reserved for flags.
> See Documentation/devicetree/bindings/arm/arch_timer.txt.
> Note that this issue is not seems to be critical as when checking
> /proc/irq/3/smp_affinity with 32 cores all 32 bits are one.
>
> The last issue is to add support for 128 cores. This requires the usage
> of bitops and currently can be tested up to 64 cores.
>
> Signed-off-by: Shlomo Pongratz <shlomo.pongratz@toganetworks.com>
> ---
>  hw/arm/Makefile.objs               |    2 +-
>  hw/arm/virtv2.c                    |  774 +++++++++++++++++
>  hw/intc/Makefile.objs              |    2 +
>  hw/intc/arm_gic_common.c           |    2 +
>  hw/intc/arm_gicv3.c                | 1596 ++++++++++++++++++++++++++++++++++++
>  hw/intc/arm_gicv3_common.c         |  188 +++++
>  hw/intc/gicv3_internal.h           |  153 ++++
>  include/hw/intc/arm_gicv3.h        |   44 +
>  include/hw/intc/arm_gicv3_common.h |  136 +++
>  target-arm/cpu.c                   |    1 +
>  target-arm/cpu.h                   |    6 +
>  target-arm/cpu64.c                 |   92 +++
>  target-arm/helper.c                |   12 +-
>  target-arm/psci.c                  |   18 +-
>  target-arm/translate-a64.c         |   14 +
>  15 files changed, 3034 insertions(+), 6 deletions(-)
>  create mode 100644 hw/arm/virtv2.c
>  create mode 100644 hw/intc/arm_gicv3.c
>  create mode 100644 hw/intc/arm_gicv3_common.c
>  create mode 100644 hw/intc/gicv3_internal.h
>  create mode 100644 include/hw/intc/arm_gicv3.h
>  create mode 100644 include/hw/intc/arm_gicv3_common.h

This is way too big to review as a single patch; you should
find a way to split it into a series of multiple coherent patches.

thanks
-- PMM

  reply	other threads:[~2015-03-09 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 14:41 [Qemu-devel] [PATCH RFC] Implement GIC-500 from GICv3 family for arm64 shlomo.pongratz
2015-03-09 15:13 ` Peter Maydell [this message]
2015-03-10  9:30   ` Shlomo Pongratz
2015-03-10  1:18 ` Shannon Zhao
2015-03-10  9:34   ` Shlomo Pongratz
2015-03-10  9:50     ` Shannon Zhao
2015-03-10  9:59       ` Claudio Fontana
2015-03-10  7:06 ` Pei XiaoYong
2015-03-10  9:47   ` Shlomo Pongratz
2015-03-10 15:01     ` michael
  -- strict thread matches above, loose matches on Subject: below --
2015-03-09 14:54 shlomo.pongratz

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=CAFEAcA8zkno-jJEkV2RCWeSX1swiYaLgOcJVSF1PFP-Ww6pCEA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=claudio.fontana@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    --cc=shlomo.pongratz@toganetworks.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).