From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com, nrb@linux.ibm.com
Subject: [kvm-unit-tests 0/2] s390x: Fixup test fencing
Date: Tue, 4 Aug 2026 14:16:27 +0000 [thread overview]
Message-ID: <20260804142133.1745878-1-frankja@linux.ibm.com> (raw)
Migration tests have been fenced for way too long in TCG due to a TCG
bug that has been fixed ages ago.
The skey access tests will always fail in TCG so it makes more sense
to fence them in the test itself rather than to filter the CI results
so that humans won't see the fail.
Janosch Frank (2):
s390x: unittests: Reenable tcg for migration tests
s390x: skey: Fence TCG protection checks
s390x/skey.c | 8 ++++++++
s390x/unittests.cfg | 5 -----
2 files changed, 8 insertions(+), 5 deletions(-)
--
2.53.0
next reply other threads:[~2026-08-04 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 14:16 Janosch Frank [this message]
2026-08-04 14:16 ` [kvm-unit-tests 1/2] s390x: unittests: Reenable tcg for migration tests Janosch Frank
2026-08-04 14:16 ` [kvm-unit-tests 2/2] s390x: skey: Fence TCG protection checks Janosch Frank
2026-08-06 8:38 ` Claudio Imbrenda
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=20260804142133.1745878-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.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