From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
thuth@redhat.com, david@redhat.com, nrb@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 1/2] s390x: diag10: Fence tcg and pv environments
Date: Wed, 28 May 2025 14:02:46 +0200 [thread overview]
Message-ID: <20250528140246.1c32e996@p-imbrenda> (raw)
In-Reply-To: <2706494c-a033-4956-bf72-d9acf3b6d89b@linux.ibm.com>
On Wed, 28 May 2025 13:13:45 +0200
Janosch Frank <frankja@linux.ibm.com> wrote:
> On 5/28/25 11:41 AM, Claudio Imbrenda wrote:
> > On Wed, 28 May 2025 09:13:49 +0000
> > Janosch Frank <frankja@linux.ibm.com> wrote:
> >
> >> Diag10 isn't supported under either of these environments so let's
> >> make sure that the test bails out accordingly.
> >
> > does KVM always implement diag10?
>
> It was introduced October of 2011 and there's no way of disabling it
> that I can see.
>
> >
> > is there no other way to check whether diag10 is available?
>
> The z/VM CP programming services doesn't specify a feature bit or any
> other way to check as far as I can see.
>
> >
> > we could, for example, try to run it "correctly" and see whether we get
> > a Specification exception, and then fence.
>
> We could move the content test to the top and bail out if there's a
> spec. That would allow us to handle the addition of diag10 support for
> TCG without a test change.
>
> But:
> How likely is it that we want to implement diag10 in TCG?
> My guess is that adding it to PV is even less likely.
> Not running them under PV and TCG gives us back some CI time although
> it's likely minuscule.
fair points
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
next prev parent reply other threads:[~2025-05-28 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 9:13 [kvm-unit-tests PATCH 0/2] s390x: diag10: Fixup Janosch Frank
2025-05-28 9:13 ` [kvm-unit-tests PATCH 1/2] s390x: diag10: Fence tcg and pv environments Janosch Frank
2025-05-28 9:41 ` Claudio Imbrenda
2025-05-28 11:13 ` Janosch Frank
2025-05-28 12:02 ` Claudio Imbrenda [this message]
2025-05-28 9:55 ` Thomas Huth
2025-05-28 10:59 ` Janosch Frank
2025-05-28 14:50 ` Nico Boehr
2025-05-28 9:13 ` [kvm-unit-tests PATCH 2/2] s390x: diag10: Check page clear Janosch Frank
2025-05-28 9:42 ` Claudio Imbrenda
2025-05-28 14:56 ` Nico Boehr
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=20250528140246.1c32e996@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).