Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gautam Gala" <ggala@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v1 2/2] KVM: s390: selftests: Add vsie validity interception tests
Date: Thu, 19 Nov 2026 12:58:04 +0000	[thread overview]
Message-ID: <sashiko-outbox-223127@kernel.org> (raw)
In-Reply-To: <20261119124936.33396-3-ggala@linux.ibm.com>

> Add tests for validity interceptions raised during vsie shadow SCB
> setup. An interception raised before any guest 3 state has been copied
> into the shadow SCB must report only the interception data (icptcode,
> ipa, ipb) to guest 2. It must not write back guest 3 state, in
> particular cpuflags, ihcpu and icptstatus.
> 
> Check the early validity interception with a new and a cached vsie
> page, for the RRF, SLSV, GED+GED2 and ESA mode cases. The cached case
> leaves stale state in the shadow SCB (for example a non-zero
> icptstatus), so that a bogus write back to guest 2 is detected.
> 
> Also check that a valid guest 3 still has its state written back, and
> that validity interceptions raised later (shadow_crycb(), pin_blocks(),
> unmapped prefix) still report the reason code and leave the SCB
> unchanged.
> 
> The early validity cases fail without the preceding vsie fix. Skip the
> test if SIEF2 is not available, and skip the GED+GED2 and CRYCB cases
> if facility 78 or 76 is missing.
> 
> Signed-off-by: Gautam Gala <ggala@linux.ibm.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261119124936.33396-1-ggala@linux.ibm.com?part=2


      reply	other threads:[~2026-11-19 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 12:49 [PATCH v1 0/2] KVM: s390: vsie: Do not overwrite guest 3 state on early validity icpt Gautam Gala
2026-11-19 12:49 ` [PATCH v1 1/2] " Gautam Gala
2026-11-19 12:55   ` sashiko-bot
2026-11-19 12:49 ` [PATCH v1 2/2] KVM: s390: selftests: Add vsie validity interception tests Gautam Gala
2026-11-19 12:58   ` sashiko-bot [this message]

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=sashiko-outbox-223127@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=ggala@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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