From: Thomas Huth <thuth@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
qemu-s390x@nongnu.org
Cc: frankja@linux.ibm.com
Subject: Re: [PATCH v2 1/2] s390x: intercept: fence one test when using TCG
Date: Thu, 21 Jul 2022 15:41:30 +0200 [thread overview]
Message-ID: <b250461b-ee09-d499-e5a4-4a9a303bed66@redhat.com> (raw)
In-Reply-To: <20220721133002.142897-2-imbrenda@linux.ibm.com>
On 21/07/2022 15.30, Claudio Imbrenda wrote:
> Qemu commit f8333de2793 ("target/s390x/tcg: SPX: check validity of new prefix")
> fixes a TCG bug discovered with a new testcase in the intercept test.
>
> The gitlab pipeline for the KVM unit tests uses TCG and it will keep
> failing every time as long as the pipeline uses a version of Qemu
> without the aforementioned patch.
>
> Fence the specific testcase for now. Once the pipeline is fixed, this
> patch can safely be reverted.
>
> This patch is meant to go on top this already queued patch from Janis:
> "s390x/intercept: Test invalid prefix argument to SET PREFIX"
> https://lore.kernel.org/all/20220627152412.2243255-1-scgl@linux.ibm.com/
If we keep this as a separate patch, that paragraph should be removed from
the commit description.
Anyway:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2022-07-21 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:30 [PATCH v2 0/2] s390x: Pipeline and other minor fixes Claudio Imbrenda
2022-07-21 13:30 ` [PATCH v2 1/2] s390x: intercept: fence one test when using TCG Claudio Imbrenda
2022-07-21 13:41 ` Thomas Huth [this message]
2022-07-21 13:46 ` Claudio Imbrenda
2022-07-21 13:30 ` [PATCH v2 2/2] s390x: intercept: make sure all output lines are unique Claudio Imbrenda
2022-07-21 13:42 ` Thomas Huth
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=b250461b-ee09-d499-e5a4-4a9a303bed66@redhat.com \
--to=thuth@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=qemu-s390x@nongnu.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