From: "Alex Bennée" <alex.bennee@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, maz@kernel.org, shashi.mallela@linaro.org,
qemu-arm@nongnu.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, eric.auger@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 0/3] GIC ITS tests
Date: Fri, 19 Nov 2021 16:30:47 +0000 [thread overview]
Message-ID: <877dd4umy6.fsf@linaro.org> (raw)
In-Reply-To: <20211112145442.5ktlpwyolwdsxlnx@gator.home>
Andrew Jones <drjones@redhat.com> writes:
> On Fri, Nov 12, 2021 at 02:08:01PM +0000, Alex Bennée wrote:
>>
>> Andrew Jones <drjones@redhat.com> writes:
>>
>> > On Fri, Nov 12, 2021 at 11:47:31AM +0000, Alex Bennée wrote:
>> >> Hi,
>> >>
>> >> Sorry this has been sitting in my tree so long. The changes are fairly
>> >> minor from v2. I no longer split the tests up into TCG and KVM
>> >> versions and instead just ensure that ERRATA_FORCE is always set when
>> >> run under TCG.
>> >>
>> >> Alex Bennée (3):
>> >> arm64: remove invalid check from its-trigger test
>> >> arm64: enable its-migration tests for TCG
>> >> arch-run: do not process ERRATA when running under TCG
>> >>
>> >> scripts/arch-run.bash | 4 +++-
>> >> arm/gic.c | 16 ++++++----------
>> >> arm/unittests.cfg | 3 ---
>> >> 3 files changed, 9 insertions(+), 14 deletions(-)
>> >>
>> >> --
>> >> 2.30.2
>> >>
>> >> _______________________________________________
>> >> kvmarm mailing list
>> >> kvmarm@lists.cs.columbia.edu
>> >> https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
>> >
>> > Hi Alex,
>> >
>> > Thanks for this. I've applied to arm/queue, but I see that
>> >
>> > FAIL: gicv3: its-trigger: inv/invall: dev2/eventid=20 pending LPI is received
>> >
>> > consistently fails for me. Is that expected? Does it work for you?
>>
>> doh - looks like I cocked up the merge conflict...
>>
>> Did it fail for TCG or for KVM (or both)?
>
> Just TCG, which was why I was wondering if it was expected. I've never run
> these tests with TCG before.
Hmm I think expecting the IRQ at all is broken so I think I should
delete the whole pending test.
>
> Thanks,
> drew
--
Alex Bennée
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-19 16:32 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 ` [kvm-unit-tests PATCH v3 1/3] arm64: remove invalid check from its-trigger test Alex Bennée
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 [this message]
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=877dd4umy6.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=drjones@redhat.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).