From: Peter Maydell <peter.maydell@linaro.org>
To: Shlomo Pongratz <shlomopongratz@gmail.com>
Cc: Eric Auger <eric.auger@linaro.org>,
Shlomo Pongratz <shlomo.pongratz@huawei.com>,
Pavel Fedin <p.fedin@samsung.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Shannon Zhao <shannon.zhao@linaro.org>,
Ashok Kumar <ashoks@broadcom.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC V4 0/4] Implement GIC-500 from GICv3 family for arm64
Date: Thu, 17 Sep 2015 18:52:04 +0100 [thread overview]
Message-ID: <CAFEAcA_+8YLfX8O1_T4PkXZUhBQVR4AOEPz-Ga_XL8SQuFd0XQ@mail.gmail.com> (raw)
In-Reply-To: <1442511496-24050-1-git-send-email-shlomopongratz@gmail.com>
On 17 September 2015 at 18:38, Shlomo Pongratz <shlomopongratz@gmail.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.
> This is because 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.
>
> Things left to do:
>
> Support SPI, note that this patch porpose is to enable running 64 cores using
> the "virt" virtual machine.
>
> Add support for 128 cores. This requires the usage
> of bitops which requires a major rewrite.
>
> Special thanks to Peter Crostwaite whose patch to th Linux (kernel) i.e.
> Implement cpu_relax as yield solved the problem of the boot process getting
> stuck for 24 cores and more.
This still seems to have the same issues as were noted in previous
rounds:
* you need to get rid of the limitation on number of cores. There
should be no hard limit imposed by the GIC emulation code: not
64, not 128, not anything.
* patch 2 is over 2000 lines, which is far too big to review. It
needs to be split up. Aim for 200 lines per patch at maximum;
smaller is better.
Also, patch 4 looks like it's an older version of one of Pavel's;
you probably want to rebase on top of Pavel's recent v14 series,
which is nearly ready to go into master.
thanks
-- PMM
next prev parent reply other threads:[~2015-09-17 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 17:38 [Qemu-devel] [PATCH RFC V4 0/4] Implement GIC-500 from GICv3 family for arm64 Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 1/4] hw/intc: Implement GIC-500 support files Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 2/4] hw/intc: Implment GIC-500 Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 3/4] target-arm/cpu64 GICv3 system instructions support Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 4/4] Add virt-v3 machine that uses GIC-500 Shlomo Pongratz
2015-09-24 18:03 ` Christopher Covington
2015-09-24 19:16 ` Christopher Covington
2015-09-28 15:20 ` Shlomo Pongratz
2015-09-17 17:52 ` Peter Maydell [this message]
2015-09-17 18:18 ` [Qemu-devel] [PATCH RFC V4 0/4] Implement GIC-500 from GICv3 family for arm64 Shlomo Pongratz
2015-09-17 18:33 ` Peter Maydell
2015-09-17 18:54 ` Shlomo Pongratz
2015-09-17 19:03 ` Peter Maydell
2015-09-24 9:55 ` Pavel Fedin
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=CAFEAcA_+8YLfX8O1_T4PkXZUhBQVR4AOEPz-Ga_XL8SQuFd0XQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=ashoks@broadcom.com \
--cc=eric.auger@linaro.org \
--cc=imammedo@redhat.com \
--cc=p.fedin@samsung.com \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=shlomo.pongratz@huawei.com \
--cc=shlomopongratz@gmail.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).