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, seiden@linux.ibm.com, nrb@linux.ibm.com,
nsg@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 2/3] s390x: pv: Test sie entry intercepts and validities
Date: Tue, 28 Feb 2023 18:19:34 +0100 [thread overview]
Message-ID: <20230228181934.24c573df@p-imbrenda> (raw)
In-Reply-To: <95184ea5-7451-934d-8988-54f0eeec99f1@linux.ibm.com>
On Tue, 21 Feb 2023 10:22:13 +0100
Janosch Frank <frankja@linux.ibm.com> wrote:
[...]
> >> + /* Yes I know this is not reliable as one cpu might overwrite it */
> >
> > the wording in this comment could be improved
>
> How about:
> This might not be fully reliable but it should be sufficient for our
> current goals.
looks good, thanks
>
> [...]
>
> >> + report_prefix_push("shared");
> >> + sie(&vm);
> >> + /* Guest indicates that it has shared the new lowcore */
> >> + report(vm.sblk->icptcode == ICPT_PV_NOTIFY && vm.sblk->ipa == 0x8302 &&
> >> + vm.sblk->ipb == 0x50000000 && vm.save_area.guest.grs[5] == 0x44,
> >> + "intercept values");
> >> +
> >> + uv_export(vm.sblk->mso + lc_off);
> >> + uv_export(vm.sblk->mso + lc_off + PAGE_SIZE);
> >
> > why are you not testing both pages individually here, like you did
> > above?
>
> Hmm, I don't think there was a reason behind this. I'll add it.
>
> [...]
next prev parent reply other threads:[~2023-02-28 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 8:48 [kvm-unit-tests PATCH 0/3] s390x: Add PV SIE intercepts and ipl tests Janosch Frank
2023-02-01 8:48 ` [kvm-unit-tests PATCH 1/3] lib: s390x: Introduce UV validity function Janosch Frank
2023-02-01 8:48 ` [kvm-unit-tests PATCH 2/3] s390x: pv: Test sie entry intercepts and validities Janosch Frank
2023-02-15 17:06 ` Claudio Imbrenda
2023-02-21 9:22 ` Janosch Frank
2023-02-28 17:19 ` Claudio Imbrenda [this message]
2023-02-01 8:48 ` [kvm-unit-tests PATCH 3/3] s390x: pv: Add IPL reset tests Janosch Frank
2023-02-17 16:42 ` Claudio Imbrenda
2023-02-21 9:26 ` Janosch Frank
2023-02-28 17:20 ` 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=20230228181934.24c573df@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@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=seiden@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