From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Ryan Harkin <ryan.harkin@linaro.org>
Cc: Dennis Chen <dennis.chen@arm.com>,
edk2-devel-01 <edk2-devel@lists.01.org>,
nd@arm.com, Laszlo Ersek <lersek@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH] ARMPkg: Unified the GIC base address variables as 64-bit width
Date: Mon, 24 Oct 2016 17:16:44 +0100 [thread overview]
Message-ID: <CAKv+Gu-x-ZD8=afKy1BgTY5X+ox=JiM_aWxYE3xU_hUkzjZ_rQ@mail.gmail.com> (raw)
In-Reply-To: <CAD0U-h+qQbQV1OOw4YhGSxUFxs3GAUAOW15yt-Lb0z+MtnyfmA@mail.gmail.com>
On 24 October 2016 at 12:47, Ryan Harkin <ryan.harkin@linaro.org> wrote:
> On 24 October 2016 at 04:04, Dennis Chen <dennis.chen@arm.com> wrote:
>> Since ACPI spec defines the GIC base addresses (CPU interface,
>> Distributor and Redistributor*GICv3 only*) as 64-bit, so we should
>> define these corresponding base address variables as 64-bit instead of
>> 32-bit. This patch redefines them according to the ACPI spec.
>>
>
> Following on with Ard's comment on the earlier version, what happens
> if you want to use GICv3 on a 32bit system, eg the Cortex-A32 FVP
> models, which I believe [1] has GICv3?
>
I don't think that matters. GICv3 does not use MMIO for the CPU
interface anyway, and referring to the MMIO bits using 64-bit types is
unlikely to affect performance imo. From a functionality pov, those
top bits will simply be always zero (much like they are now on every
known ARM platform)
> [1] Go here and search for "gicv3"
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0834i/Chunk1955773768.html
>
prev parent reply other threads:[~2016-10-24 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 3:04 [PATCH] ARMPkg: Unified the GIC base address variables as 64-bit width Dennis Chen
2016-10-24 11:47 ` Ryan Harkin
2016-10-24 16:16 ` Ard Biesheuvel [this message]
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-list 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='CAKv+Gu-x-ZD8=afKy1BgTY5X+ox=JiM_aWxYE3xU_hUkzjZ_rQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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