arm64: gic: its-trigger: Don't trigger LPI while it is pending

The its-trigger test checks that LPI 8195 is not delivered to the CPU while
it is disabled at the ITS level, after which it is re-enabled and tests
that it's now properly asserted. After it is re-enabled it is triggered
again, which can lead to the same interrupt being delivered twice: once
after the configuration invalidation (which re-enables it) and once after
the INT command.

Get rid of the INT command after it is re-enabled to prevent the LPI from
being asserted twice and add a separate check to test that the INT command
still works for the LPI.
9 jobs for fixes1-v2 in 0 seconds (queued for 108 minutes and 22 seconds)
Status Job ID Name Coverage
  Test
failed #32
build-aarch64

failed #33
build-arm

failed #40
build-centos7

failed #39
build-clang

failed #38
build-i386

failed #34
build-ppc64be

failed #35
build-ppc64le

failed #36
build-s390x

failed #37
build-x86_64

 
Name Stage Failure
failed
build-arm Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-aarch64 Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-ppc64le Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-x86_64 Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-clang Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-centos7 Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-s390x Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-i386 Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
build-ppc64be Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log