From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Andre Przywara <andre.przywara@arm.com>,
Andrew Jones <drjones@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 17/17] arm: gic: Test Group0 SPIs
Date: Wed, 13 Nov 2019 11:26:54 +0000 [thread overview]
Message-ID: <88a5d9f9-e5fe-8025-8857-dc78a5aa791a@arm.com> (raw)
In-Reply-To: <20191108144240.204202-18-andre.przywara@arm.com>
Hi,
On 11/8/19 2:42 PM, Andre Przywara wrote:
> With the newly gained building blocks we can now actually test Group 0
> interrupts on our emulated/virtualized GIC.
> The least common denominator for the groups usage on both GICv2 and
> GICv3 is to configure group 0 interrupts to trigger FIQs, and group 1
> interrupts to trigger IRQs.
> For testing this we first configure our test SPI to belong to group 0,
> then trigger it to see that it is actually delivered as an FIQ, and not as
> an IRQ.
> The we change the group to become 1, and trigger again, this time
> expecting the opposite behaviour.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> arm/gic.c | 103 ++++++++++++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 101 insertions(+), 2 deletions(-)
>
> diff --git a/arm/gic.c b/arm/gic.c
> index 43a272b..9942314 100644
> --- a/arm/gic.c
> +++ b/arm/gic.c
> @@ -276,6 +276,22 @@ static void irqs_enable(void)
> local_irq_enable();
> }
>
> +static void fiqs_enable(void)
> +{
> +#ifdef __arm__
> + install_exception_handler(EXCPTN_FIQ, fiq_handler);
> +#else
> + install_irq_handler(EL1H_FIQ, fiq_handler);
> +#endif
> + if (gic_version() == 3) {
> + gicv3_write_grpen0(1);
> + } else {
> + gicv2_enable_fiq(true);
> + gicv2_enable_group1(true);
Why do we enable group 1 here for GICv2? The commit message says that group 1
interrupts will be delivered as IRQs.
> + }
> + local_fiq_enable();
> +}
> +
> static void ipi_send(void)
> {
> irqs_enable();
> @@ -598,6 +614,7 @@ static void spi_configure_irq(int irq, int cpu)
>
> #define IRQ_STAT_NONE 0
> #define IRQ_STAT_IRQ 1
> +#define IRQ_STAT_FIQ 2
> #define IRQ_STAT_TYPE_MASK 0x3
> #define IRQ_STAT_NO_CLEAR 4
>
> @@ -617,14 +634,21 @@ static bool trigger_and_check_spi(const char *test_name,
> cpumask_clear(&cpumask);
> switch (irq_stat & IRQ_STAT_TYPE_MASK) {
> case IRQ_STAT_NONE:
> + ret &= (check_acked(NULL, &cpumask, 0) >= 0);
> + ret &= (check_acked(test_name, &cpumask, 1) >= 0);
> break;
> case IRQ_STAT_IRQ:
> + ret &= (check_acked(NULL, &cpumask, 0) >= 0);
> + cpumask_set_cpu(cpu, &cpumask);
> + ret &= (check_acked(test_name, &cpumask, 1) >= 0);
> + break;
> + case IRQ_STAT_FIQ:
> + ret &= (check_acked(NULL, &cpumask, 1) >= 0);
> cpumask_set_cpu(cpu, &cpumask);
> + ret &= (check_acked(test_name, &cpumask, 0) >= 0);
> break;
> }
>
> - ret = (check_acked(test_name, &cpumask, 1) >= 0);
> -
> /* Clean up pending bit in case this IRQ wasn't taken. */
> if (!(irq_stat & IRQ_STAT_NO_CLEAR))
> gic_set_irq_bit(SPI_IRQ, GICD_ICPENDR);
> @@ -657,6 +681,9 @@ static void spi_test_smp(void)
> int cpu;
> int cores = 1;
>
> + if (nr_cpus > 8)
> + printf("triggering SPIs on all %d cores, takes %d seconds\n",
> + nr_cpus, (nr_cpus - 1) * 3 / 2);
Can you explain how you got the elapsed time for triggering SPIs?
> wait_on_ready();
> for_each_present_cpu(cpu) {
> if (cpu == smp_processor_id())
> @@ -671,6 +698,46 @@ static void spi_test_smp(void)
> }
>
> #define GICD_CTLR_ENABLE_BOTH (GICD_CTLR_ENABLE_G0 | GICD_CTLR_ENABLE_G1)
> +#define EXPECT_FIQ true
> +#define EXPECT_IRQ false
> +
> +/*
> + * Check whether our SPI interrupt is correctly delivered as an FIQ or as
> + * an IRQ, as configured.
> + * This tries to enable the two groups independently, to check whether
> + * the relation group0->FIQ and group1->IRQ holds.
> + */
> +static void gic_check_irq_delivery(void *gicd_base, bool as_fiq)
The function also checks for FIQs, as alluded to by the as_fiq parameter; also,
most of the function does different things based on that parameter. I think it
would be cleaner to split it into two functions, gic_check_irq_delivery and
gic_check_fiq_delivery. That way you can have more clearer messages for
trigger_and_check_spi and you get rid of the two defines above. At the very least,
it should be renamed to something more appropriate for what it does, like
gic_check_int_delivery.
> +{
> + u32 reg = readl(gicd_base + GICD_CTLR) & ~GICD_CTLR_ENABLE_BOTH;
> + int cpu = smp_processor_id();
> +
> + /* Check that both groups disabled block the IRQ. */
> + writel(reg, gicd_base + GICD_CTLR);
> + trigger_and_check_spi("no IRQs with both groups disabled",
> + IRQ_STAT_NONE, cpu);
> +
> + /* Check that just the *other* group enabled blocks the IRQ. */
> + if (as_fiq)
> + writel(reg | GICD_CTLR_ENABLE_G1, gicd_base + GICD_CTLR);
> + else
> + writel(reg | GICD_CTLR_ENABLE_G0, gicd_base + GICD_CTLR);
> + trigger_and_check_spi("no IRQs with just the other group enabled",
> + IRQ_STAT_NONE, cpu);
> +
> + /* Check that just this group enabled fires the IRQ. */
> + if (as_fiq)
> + writel(reg | GICD_CTLR_ENABLE_G0, gicd_base + GICD_CTLR);
> + else
> + writel(reg | GICD_CTLR_ENABLE_G1, gicd_base + GICD_CTLR);
> + trigger_and_check_spi("just this group enabled",
> + as_fiq ? IRQ_STAT_FIQ : IRQ_STAT_IRQ, cpu);
> +
> + /* Check that both groups enabled fires the IRQ. */
> + writel(reg | GICD_CTLR_ENABLE_BOTH, gicd_base + GICD_CTLR);
> + trigger_and_check_spi("both groups enabled",
> + as_fiq ? IRQ_STAT_FIQ : IRQ_STAT_IRQ, cpu);
> +}
>
> /*
> * Check the security state configuration of the GIC.
> @@ -711,6 +778,9 @@ static bool gicv3_check_security(void *gicd_base)
> * Check whether this works as expected (as Linux will not use this feature).
> * We can only verify this state on a GICv3, so we check it there and silently
> * assume it's valid for GICv2.
> + * GICv2 and GICv3 handle the groups differently, but we use the common
> + * denominator (Group0 as FIQ, Group1 as IRQ) and rely on the GIC library for
> + * abstraction.
> */
> static void test_irq_group(void *gicd_base)
> {
> @@ -754,6 +824,35 @@ static void test_irq_group(void *gicd_base)
> gic_set_irq_group(SPI_IRQ, !reg);
> report("IGROUPR is writable", gic_get_irq_group(SPI_IRQ) != reg);
> gic_set_irq_group(SPI_IRQ, reg);
> +
> + /*
> + * Configure group 0 interrupts as FIQs, install both an FIQ and IRQ
> + * handler and allow both types to be delivered to the core.
> + */
> + irqs_enable();
> + fiqs_enable();
> +
> + /* Configure one SPI to be a group0 interrupt. */
> + gic_set_irq_group(SPI_IRQ, 0);
> + spi_configure_irq(SPI_IRQ, smp_processor_id());
> + report_prefix_push("FIQ");
> + gic_check_irq_delivery(gicd_base, EXPECT_FIQ);
> + report_prefix_pop();
> +
> + /* Configure the SPI to be a group1 interrupt instead. */
> + gic_set_irq_group(SPI_IRQ, 1);
> + report_prefix_push("IRQ");
> + gic_check_irq_delivery(gicd_base, EXPECT_IRQ);
> + report_prefix_pop();
> +
> + /* Reset the IRQ to the default group. */
> + if (is_gicv3)
> + gic_set_irq_group(SPI_IRQ, 1);
> + else
> + gic_set_irq_group(SPI_IRQ, 0);
> + gic_disable_irq(SPI_IRQ);
> +
> + report_prefix_pop();
> }
>
> static void spi_send(void)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-13 11:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:42 [kvm-unit-tests PATCH 00/17] arm: gic: Test SPIs and interrupt groups Andre Przywara
2019-11-08 14:42 ` [kvm-unit-tests PATCH 01/17] arm: gic: Enable GIC MMIO tests for GICv3 as well Andre Przywara
2019-11-08 17:28 ` Alexandru Elisei
2019-11-12 12:49 ` Auger Eric
2019-11-08 14:42 ` [kvm-unit-tests PATCH 02/17] arm: gic: Generalise function names Andre Przywara
2019-11-12 11:11 ` Alexandru Elisei
2019-11-12 12:49 ` Auger Eric
2019-11-08 14:42 ` [kvm-unit-tests PATCH 03/17] arm: gic: Provide per-IRQ helper functions Andre Przywara
2019-11-12 12:51 ` Alexandru Elisei
2019-11-12 15:53 ` Auger Eric
2019-11-12 16:53 ` Alexandru Elisei
2019-11-12 13:49 ` Auger Eric
2019-11-08 14:42 ` [kvm-unit-tests PATCH 04/17] arm: gic: Support no IRQs test case Andre Przywara
2019-11-12 13:26 ` Alexandru Elisei
2019-11-12 21:14 ` Auger Eric
2019-11-08 14:42 ` [kvm-unit-tests PATCH 05/17] arm: gic: Prepare IRQ handler for handling SPIs Andre Przywara
2019-11-12 13:36 ` Alexandru Elisei
2019-11-12 20:56 ` Auger Eric
2019-11-08 14:42 ` [kvm-unit-tests PATCH 06/17] arm: gic: Add simple shared IRQ test Andre Przywara
2019-11-12 13:54 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 07/17] arm: gic: Extend check_acked() to allow silent call Andre Przywara
2019-11-12 15:23 ` Alexandru Elisei
2019-11-14 12:32 ` Andrew Jones
2019-11-15 11:32 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 08/17] arm: gic: Add simple SPI MP test Andre Przywara
2019-11-12 15:41 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 09/17] arm: gic: Add test for flipping GICD_CTLR.DS Andre Przywara
2019-11-12 16:42 ` Alexandru Elisei
2019-11-14 13:39 ` Vladimir Murzin
2019-11-14 14:17 ` Andre Przywara
2019-11-14 14:50 ` Vladimir Murzin
2019-11-14 15:21 ` Alexandru Elisei
2019-11-14 15:27 ` Peter Maydell
2019-11-14 15:47 ` Alexandru Elisei
2019-11-14 15:56 ` Peter Maydell
2019-11-08 14:42 ` [kvm-unit-tests PATCH 10/17] arm: gic: Check for writable IGROUPR registers Andre Przywara
2019-11-12 16:51 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 11/17] arm: gic: Check for validity of both group enable bits Andre Przywara
2019-11-12 16:58 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 12/17] arm: gic: Change gic_read_iar() to take group parameter Andre Przywara
2019-11-12 17:19 ` Alexandru Elisei
2019-11-14 12:50 ` Andrew Jones
2019-11-08 14:42 ` [kvm-unit-tests PATCH 13/17] arm: gic: Change write_eoir() " Andre Przywara
2019-11-08 14:42 ` [kvm-unit-tests PATCH 14/17] arm: gic: Prepare for receiving GIC group 0 interrupts via FIQs Andre Przywara
2019-11-12 17:30 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 15/17] arm: gic: Provide FIQ handler Andre Przywara
2019-11-13 10:14 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 16/17] arm: gic: Prepare interrupt statistics for both groups Andre Przywara
2019-11-13 10:44 ` Alexandru Elisei
2019-11-08 14:42 ` [kvm-unit-tests PATCH 17/17] arm: gic: Test Group0 SPIs Andre Przywara
2019-11-13 11:26 ` Alexandru Elisei [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-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=88a5d9f9-e5fe-8025-8857-dc78a5aa791a@arm.com \
--to=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.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).