public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Nina Schoetterl-Glausch" <nsg@linux.ibm.com>,
	"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"Nico Böhr" <nrb@linux.ibm.com>,
	"Janosch Frank" <frankja@linux.ibm.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Andrew Jones" <andrew.jones@linux.dev>,
	"David Hildenbrand" <david@redhat.com>, <kvm@vger.kernel.org>,
	<linux-s390@vger.kernel.org>
Subject: Re: [kvm-unit-tests PATCH v3 4/7] s390x: Add function for checking diagnose intercepts
Date: Wed, 26 Jun 2024 09:52:22 +1000	[thread overview]
Message-ID: <D29I39HGFVVG.3IRU89PEXG7YM@gmail.com> (raw)
In-Reply-To: <12c7ba9be7804d31f4aaa4bd804716732add1561.camel@linux.ibm.com>

On Tue Jun 25, 2024 at 6:11 PM AEST, Nina Schoetterl-Glausch wrote:
> On Tue, 2024-06-25 at 12:14 +1000, Nicholas Piggin wrote:
> > On Fri Jun 21, 2024 at 12:16 AM AEST, Nina Schoetterl-Glausch wrote:
> > > sie_is_diag_icpt() checks if the intercept is due to an expected
> > > diagnose call and is valid.
> > > It subsumes pv_icptdata_check_diag.
> > > 
> > > Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> > > ---
> > >  lib/s390x/pv_icptdata.h | 42 --------------------------------
> > >  lib/s390x/sie.h         | 12 ++++++++++
> > >  lib/s390x/sie.c         | 53 +++++++++++++++++++++++++++++++++++++++++
> > >  s390x/pv-diags.c        |  8 +++----
> > >  s390x/pv-icptcode.c     | 11 ++++-----
> > >  s390x/pv-ipl.c          |  7 +++---
> > >  6 files changed, 76 insertions(+), 57 deletions(-)
> > >  delete mode 100644 lib/s390x/pv_icptdata.h
>
> [...]
>
> > > +bool sie_is_diag_icpt(struct vm *vm, unsigned int diag)
> > > +{
> > > +	union {
> > > +		struct {
> > > +			uint64_t     : 16;
> > > +			uint64_t ipa : 16;
> > > +			uint64_t ipb : 32;
> > > +		};
> > > +		struct {
> > > +			uint64_t          : 16;
> > > +			uint64_t opcode   :  8;
> > > +			uint64_t r_1      :  4;
> > > +			uint64_t r_2      :  4;
> > > +			uint64_t r_base   :  4;
> > > +			uint64_t displace : 12;
> > > +			uint64_t zero     : 16;
> > > +		};
> > > +	} instr = { .ipa = vm->sblk->ipa, .ipb = vm->sblk->ipb };
> > > +	uint8_t icptcode;
> > > +	uint64_t code;
> > > +
> > > +	switch (diag) {
> > > +	case 0x44:
> > > +	case 0x9c:
> > > +	case 0x288:
> > > +	case 0x308:
> > > +		icptcode = ICPT_PV_NOTIFY;
> > > +		break;
> > > +	case 0x500:
> > > +		icptcode = ICPT_PV_INSTR;
> > > +		break;
> > > +	default:
> > > +		/* If a new diag is introduced add it to the cases above! */
> > > +		assert_msg(false, "unknown diag");
> > > +	}
> > > +
> > > +	if (sie_is_pv(vm)) {
> > > +		if (instr.r_1 != 0 || instr.r_2 != 2 || instr.r_base != 5)
> > > +			return false;
> > > +		if (instr.displace)
> > > +			return false;
> > > +	} else {
> > > +		icptcode = ICPT_INST;
> > > +	}
> > > +	if (vm->sblk->icptcode != icptcode)
> > > +		return false;
> > > +	if (instr.opcode != 0x83 || instr.zero)
> > > +		return false;
> > > +	code = instr.r_base ? vm->save_area.guest.grs[instr.r_base] : 0;
> > > +	code = (code + instr.displace) & 0xffff;
> > > +	return code == diag;
> > > +}
> > 
> > It looks like this transformation is equivalent for the PV case.
>
> Yes, the PV case just has hardcoded values that we want to check.
>
> > You
> > could put the switch into the sie_is_pv() branch? Otherwise looks okay.
>
> I want to validate diag for both PV and non PV.

To make sure it is one of listed cases, okay I missed that
point. All those same diag numbers are valid for !PV?
In that case it's fine.

Thanks,
Nick

  reply	other threads:[~2024-06-25 23:52 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 14:16 [kvm-unit-tests PATCH v3 0/7] s390x: STFLE nested interpretation Nina Schoetterl-Glausch
2024-06-20 14:16 ` [kvm-unit-tests PATCH v3 1/7] lib: Add pseudo random functions Nina Schoetterl-Glausch
2024-06-25  3:08   ` Nicholas Piggin
2024-06-25  7:06     ` Nina Schoetterl-Glausch
2024-08-12 14:17   ` Andrew Jones
2024-10-10  8:25   ` Nico Boehr
2024-10-10  8:37     ` Andrew Jones
2024-06-20 14:16 ` [kvm-unit-tests PATCH v3 2/7] s390x: lib: Remove double include Nina Schoetterl-Glausch
2024-06-21  6:58   ` Janosch Frank
2024-06-20 14:16 ` [kvm-unit-tests PATCH v3 3/7] s390x: Add sie_is_pv Nina Schoetterl-Glausch
2024-06-20 16:41   ` Claudio Imbrenda
2024-06-21  6:59   ` Janosch Frank
2024-06-25  1:58   ` Nicholas Piggin
2024-06-20 14:16 ` [kvm-unit-tests PATCH v3 4/7] s390x: Add function for checking diagnose intercepts Nina Schoetterl-Glausch
2024-06-20 16:47   ` Claudio Imbrenda
2024-06-20 17:46     ` Nina Schoetterl-Glausch
2024-06-21  7:13   ` Janosch Frank
2024-06-25  2:14   ` Nicholas Piggin
2024-06-25  8:11     ` Nina Schoetterl-Glausch
2024-06-25 23:52       ` Nicholas Piggin [this message]
2024-06-20 14:16 ` [kvm-unit-tests PATCH v3 5/7] s390x: Add library functions for exiting from snippet Nina Schoetterl-Glausch
2024-06-20 16:55   ` Claudio Imbrenda
2024-06-20 17:16     ` Nina Schoetterl-Glausch
2024-06-20 17:26       ` Claudio Imbrenda
2024-06-25  3:13         ` Nicholas Piggin
2024-06-25  2:43   ` Nicholas Piggin
2024-10-16 14:42     ` Nina Schoetterl-Glausch
2024-06-25  2:57   ` Nicholas Piggin
2024-06-25  9:21     ` Claudio Imbrenda
2024-06-20 14:16 ` [kvm-unit-tests PATCH v3 6/7] s390x: Use library functions for snippet exit Nina Schoetterl-Glausch
2024-06-20 16:56   ` Claudio Imbrenda
2024-06-25  2:58   ` Nicholas Piggin
2024-06-20 14:17 ` [kvm-unit-tests PATCH v3 7/7] s390x: Add test for STFLE interpretive execution (format-0) Nina Schoetterl-Glausch
2024-06-20 17:25   ` Claudio Imbrenda
2024-06-20 17:42     ` Nina Schoetterl-Glausch
2024-06-25  3:11   ` Nicholas Piggin
2024-08-27 14:08   ` Nico Boehr
2024-09-02 14:24     ` Nina Schoetterl-Glausch
2024-09-03 10:46       ` Heiko Carstens
2024-10-10  8:27       ` Nico Boehr
2024-10-15 11:01         ` Nina Schoetterl-Glausch

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=D29I39HGFVVG.3IRU89PEXG7YM@gmail.com \
    --to=npiggin@gmail.com \
    --cc=andrew.jones@linux.dev \
    --cc=david@redhat.com \
    --cc=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 \
    --cc=nsg@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