From: "Alex Bennée" <alex.bennee@linaro.org>
To: kvm@vger.kernel.org
Cc: shashi.mallela@linaro.org, alexandru.elisei@arm.com,
eric.auger@redhat.com, qemu-arm@nongnu.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, christoffer.dall@arm.com,
maz@kernel.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [kvm-unit-tests PATCH v3 1/3] arm64: remove invalid check from its-trigger test
Date: Fri, 12 Nov 2021 11:47:32 +0000 [thread overview]
Message-ID: <20211112114734.3058678-2-alex.bennee@linaro.org> (raw)
In-Reply-To: <20211112114734.3058678-1-alex.bennee@linaro.org>
While an IRQ is not "guaranteed to be visible until an appropriate
invalidation" it doesn't stop the actual implementation delivering it
earlier if it wants to. This is the case for QEMU's TCG and as tests
should only be checking architectural compliance this check is
invalid.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Cc: Shashi Mallela <shashi.mallela@linaro.org>
Message-Id: <20210525172628.2088-2-alex.bennee@linaro.org>
---
v3
- reflow the comment, drop "willingly do not call" as per Eric's suggestion
---
arm/gic.c | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/arm/gic.c b/arm/gic.c
index 98135ef..1e3ea80 100644
--- a/arm/gic.c
+++ b/arm/gic.c
@@ -732,21 +732,17 @@ static void test_its_trigger(void)
"dev2/eventid=20 does not trigger any LPI");
/*
- * re-enable the LPI but willingly do not call invall
- * so the change in config is not taken into account.
- * The LPI should not hit
+ * re-enable the LPI. While "A change to the LPI configuration
+ * is not guaranteed to be visible until an appropriate
+ * invalidation operation has completed" hardware that doesn't
+ * implement caches may have delivered the event at any point
+ * after the enabling. Check the LPI has hit by the time the
+ * invall is done.
*/
gicv3_lpi_set_config(8195, LPI_PROP_DEFAULT);
stats_reset();
cpumask_clear(&mask);
its_send_int(dev2, 20);
- wait_for_interrupts(&mask);
- report(check_acked(&mask, -1, -1),
- "dev2/eventid=20 still does not trigger any LPI");
-
- /* Now call the invall and check the LPI hits */
- stats_reset();
- cpumask_clear(&mask);
cpumask_set_cpu(3, &mask);
its_send_invall(col3);
wait_for_interrupts(&mask);
--
2.30.2
next prev parent reply other threads:[~2021-11-12 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 11:47 [kvm-unit-tests PATCH v3 0/3] GIC ITS tests Alex Bennée
2021-11-12 11:47 ` Alex Bennée [this message]
2021-11-12 11:47 ` [kvm-unit-tests PATCH v3 2/3] arm64: enable its-migration tests for TCG Alex Bennée
2021-11-12 11:47 ` [kvm-unit-tests PATCH v3 3/3] arch-run: do not process ERRATA when running under TCG Alex Bennée
2021-11-12 13:23 ` [kvm-unit-tests PATCH v3 0/3] GIC ITS tests Andrew Jones
2021-11-12 14:08 ` Alex Bennée
2021-11-12 14:54 ` Andrew Jones
2021-11-19 16:30 ` Alex Bennée
2021-11-19 18:30 ` Andrew Jones
2021-11-30 14:11 ` Alex Bennée
2021-11-30 14:34 ` Andrew Jones
2022-02-01 13:10 ` Alex Bennée
2022-02-01 14:44 ` Andrew Jones
2021-11-12 14:24 ` Alex Bennée
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=20211112114734.3058678-2-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=alexandru.elisei@arm.com \
--cc=christoffer.dall@arm.com \
--cc=eric.auger@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=qemu-arm@nongnu.org \
--cc=shashi.mallela@linaro.org \
/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).