From: Laszlo Ersek <lersek@redhat.com>
To: Auger Eric <eric.auger@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Eric Auger <eric.auger.pro@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
Wei Huang <wei@redhat.com>, Andrew Jones <drjones@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@arm.com>,
Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v2 05/11] hw/arm/virt: GICv3 DT node with one or two redistributor regions
Date: Wed, 20 Jun 2018 12:38:13 +0200 [thread overview]
Message-ID: <2433d509-d833-7cbf-8e74-c3bfdab0c13b@redhat.com> (raw)
In-Reply-To: <51b9c330-ed48-e75c-0c8a-ffa8e1794e95@redhat.com>
On 06/20/18 09:10, Auger Eric wrote:
> Hi Laszlo,
>
> On 06/19/2018 09:02 PM, Ard Biesheuvel wrote:
>> On 19 June 2018 at 20:53, Laszlo Ersek <lersek@redhat.com> wrote:
>>> Hi Eric,
>>>
>>> sorry about the late followup. I have one question (mainly for Ard):
>>>
>>> On 06/15/18 16:28, Eric Auger wrote:
>>>> This patch allows the creation of a GICv3 node with 1 or 2
>>>> redistributor regions depending on the number of smu_cpus.
>>>> The second redistributor region is located just after the
>>>> existing RAM region, at 256GB and contains up to up to 512 vcpus.
>>>>
>>>> Please refer to kernel documentation for further node details:
>>>> Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt
>>>>
>>>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>>>> Reviewed-by: Andrew Jones <drjones@redhat.com>
>>>>
>>>> ---
>>>> v1 (virt3.0) -> v2
>>>> - Added Drew's R-b
>>>>
>>>> v2 -> v3:
>>>> - VIRT_GIC_REDIST2 is now 64MB large, ie. 512 redistributor capacity
>>>> - virt_gicv3_redist_region_count does not test kvm_irqchip_in_kernel
>>>> anymore
>>>> ---
>>>> hw/arm/virt.c | 29 ++++++++++++++++++++++++-----
>>>> include/hw/arm/virt.h | 14 ++++++++++++++
>>>> 2 files changed, 38 insertions(+), 5 deletions(-)
>>>>
>>>> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
>>>> index 2885d18..d9f72eb 100644
>>>> --- a/hw/arm/virt.c
>>>> +++ b/hw/arm/virt.c
>>>> @@ -148,6 +148,8 @@ static const MemMapEntry a15memmap[] = {
>>>> [VIRT_PCIE_PIO] = { 0x3eff0000, 0x00010000 },
>>>> [VIRT_PCIE_ECAM] = { 0x3f000000, 0x01000000 },
>>>> [VIRT_MEM] = { 0x40000000, RAMLIMIT_BYTES },
>>>> + /* Additional 64 MB redist region (can contain up to 512 redistributors) */
>>>> + [VIRT_GIC_REDIST2] = { 0x4000000000ULL, 0x4000000 },
>>>> /* Second PCIe window, 512GB wide at the 512GB boundary */
>>>> [VIRT_PCIE_MMIO_HIGH] = { 0x8000000000ULL, 0x8000000000ULL },
>>>> };
>>>> @@ -401,13 +403,30 @@ static void fdt_add_gic_node(VirtMachineState *vms)
>>>> qemu_fdt_setprop_cell(vms->fdt, "/intc", "#size-cells", 0x2);
>>>> qemu_fdt_setprop(vms->fdt, "/intc", "ranges", NULL, 0);
>>>> if (vms->gic_version == 3) {
>>>> + int nb_redist_regions = virt_gicv3_redist_region_count(vms);
>>>> +
>>>> qemu_fdt_setprop_string(vms->fdt, "/intc", "compatible",
>>>> "arm,gic-v3");
>>>> - qemu_fdt_setprop_sized_cells(vms->fdt, "/intc", "reg",
>>>> - 2, vms->memmap[VIRT_GIC_DIST].base,
>>>> - 2, vms->memmap[VIRT_GIC_DIST].size,
>>>> - 2, vms->memmap[VIRT_GIC_REDIST].base,
>>>> - 2, vms->memmap[VIRT_GIC_REDIST].size);
>>>> +
>>>> + qemu_fdt_setprop_cell(vms->fdt, "/intc",
>>>> + "#redistributor-regions", nb_redist_regions);
>>>> +
>>>> + if (nb_redist_regions == 1) {
>>>> + qemu_fdt_setprop_sized_cells(vms->fdt, "/intc", "reg",
>>>> + 2, vms->memmap[VIRT_GIC_DIST].base,
>>>> + 2, vms->memmap[VIRT_GIC_DIST].size,
>>>> + 2, vms->memmap[VIRT_GIC_REDIST].base,
>>>> + 2, vms->memmap[VIRT_GIC_REDIST].size);
>>>> + } else {
>>>> + qemu_fdt_setprop_sized_cells(vms->fdt, "/intc", "reg",
>>>> + 2, vms->memmap[VIRT_GIC_DIST].base,
>>>> + 2, vms->memmap[VIRT_GIC_DIST].size,
>>>> + 2, vms->memmap[VIRT_GIC_REDIST].base,
>>>> + 2, vms->memmap[VIRT_GIC_REDIST].size,
>>>> + 2, vms->memmap[VIRT_GIC_REDIST2].base,
>>>> + 2, vms->memmap[VIRT_GIC_REDIST2].size);
>>>> + }
>>>> +
>>>> if (vms->virt) {
>>>> qemu_fdt_setprop_cells(vms->fdt, "/intc", "interrupts",
>>>> GIC_FDT_IRQ_TYPE_PPI, ARCH_GICV3_MAINT_IRQ,
>>>
>>> In edk2, we have the following code in
>>> "ArmVirtPkg/Library/ArmVirtGicArchLib/ArmVirtGicArchLib.c":
>>>
>>> switch (GicRevision) {
>>>
>>> case 3:
>>> //
>>> // The GIC v3 DT binding describes a series of at least 3 physical (base
>>> // addresses, size) pairs: the distributor interface (GICD), at least one
>>> // redistributor region (GICR) containing dedicated redistributor
>>> // interfaces for all individual CPUs, and the CPU interface (GICC).
>>> // Under virtualization, we assume that the first redistributor region
>>> // listed covers the boot CPU. Also, our GICv3 driver only supports the
>>> // system register CPU interface, so we can safely ignore the MMIO version
>>> // which is listed after the sequence of redistributor interfaces.
>>> // This means we are only interested in the first two memory regions
>>> // supplied, and ignore everything else.
>>> //
>>> ASSERT (RegSize >= 32);
>>>
>>> // RegProp[0..1] == { GICD base, GICD size }
>>> DistBase = SwapBytes64 (Reg[0]);
>>> ASSERT (DistBase < MAX_UINTN);
>>>
>>> // RegProp[2..3] == { GICR base, GICR size }
>>> RedistBase = SwapBytes64 (Reg[2]);
>>> ASSERT (RedistBase < MAX_UINTN);
>>>
>>> PcdStatus = PcdSet64S (PcdGicDistributorBase, DistBase);
>>> ASSERT_RETURN_ERROR (PcdStatus);
>>> PcdStatus = PcdSet64S (PcdGicRedistributorsBase, RedistBase);
>>> ASSERT_RETURN_ERROR (PcdStatus);
>>>
>>> DEBUG ((EFI_D_INFO, "Found GIC v3 (re)distributor @ 0x%Lx (0x%Lx)\n",
>>> DistBase, RedistBase));
>>>
>>> (I vaguely recall that I may have quoted this already, but I'm not
>>> sure.)
> I don't remember you did ;-)
>>>
>>> My understanding is that this will continue working -- as long as we
>>> don't want to boot up multiple CPUs in UEFI, anyway.
>>>
>>> I think we have no plans for adding (well, for implementing)
>>> EFI_PEI_MP_SERVICES_PPI or EFI_MP_SERVICES_PROTOCOL for ARM -- do you
>>> agree, Ard?
>>>
>>
>> Yes I agree. Only the boot cpu should enter UEFI, and although there
>> are some remnants of multi core ARM stuff in the EDK2 tree, I would
>> prefer to get rid of that as soon as we can.
>>
>>> (That PPI and PROTOCOL are totally unnecessary unless it is
>>> architecturally required to configure various CPU features on each
>>> (V)CPU *individually*, before leaving the firmware. Unfortunately, x86
>>> has some CPU warts like that, and said PPI and PROTOCOL implementations
>>> for x86 have given us a good dose of grief over time. I very much hope
>>> the PPI and the PROTOCOL will never be needed on ARM!)
>>>
>>
>> That kind of configuration typically occurs in the secure firmware on
>> an ARM system, and not at all on a virtual machine.
>>
>>>
>>> Eric, I reckon you tested this patch with the ArmVirtQemu firmware too,
>>> covering both branches of the code, and with multiple VCPUs in both
>>> cases. Can you please confirm?
> I tested the high ECAM part with both 32b and 64b FW. However the
> multiple redistributor region part only was tested with 64b FW. The
> reason is Moonshot which I used to test accelerated aarch32 guest has a
> GICv2 so I can't test the GICv3 redist part on it.
>
> However if my understanding is correct as the above check only is done
> on the 1st redist, which is located in the low redist region, this
> series shouldn't introduce any regression.
I agree. Thank you!
Laszlo
next prev parent reply other threads:[~2018-06-20 10:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 14:28 [Qemu-devel] [PATCH v2 00/11] KVM/ARM: virt-3.0: Multiple redistributor regions and 256MB ECAM region Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 01/11] linux-headers: Update to 4.18-rc0 Eric Auger
2018-06-20 13:57 ` Peter Maydell
2018-06-20 14:03 ` Auger Eric
2018-06-20 14:06 ` Peter Maydell
2018-06-20 14:08 ` Auger Eric
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 02/11] target/arm: Allow KVM device address overwriting Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 03/11] hw/intc/arm_gicv3: Introduce redist-region-count array property Eric Auger
2018-06-15 15:27 ` Andrew Jones
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 04/11] hw/intc/arm_gicv3_kvm: Get prepared to handle multiple redist regions Eric Auger
2018-06-15 15:19 ` Andrew Jones
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 05/11] hw/arm/virt: GICv3 DT node with one or two redistributor regions Eric Auger
2018-06-19 18:53 ` Laszlo Ersek
2018-06-19 19:02 ` Ard Biesheuvel
2018-06-20 7:10 ` Auger Eric
2018-06-20 10:38 ` Laszlo Ersek [this message]
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 06/11] hw/arm/virt-acpi-build: Advertise one or two GICR structures Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 07/11] hw/arm/virt: Register two redistributor regions when necessary Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 08/11] hw/arm/virt: Add a new 256MB ECAM region Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 09/11] hw/arm/virt: Add virt-3.0 machine type Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 10/11] hw/arm/virt: Use 256MB ECAM region by default Eric Auger
2018-06-15 14:28 ` [Qemu-devel] [PATCH v2 11/11] hw/arm/virt: Increase max_cpus to 512 Eric Auger
2018-06-20 14:36 ` [Qemu-devel] [PATCH v2 00/11] KVM/ARM: virt-3.0: Multiple redistributor regions and 256MB ECAM region Peter Maydell
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=2433d509-d833-7cbf-8e74-c3bfdab0c13b@redhat.com \
--to=lersek@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=christoffer.dall@arm.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.com \
--cc=zhaoshenglong@huawei.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).