From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>
Cc: kvm@vger.kernel.org, Janosch Frank <frankja@linux.ibm.com>,
linux-s390@vger.kernel.org, David Hildenbrand <david@redhat.com>
Subject: Re: [kvm-unit-tests v2 PATCH] s390x: sie: Test whether the epoch extension field is working as expected
Date: Fri, 9 Dec 2022 13:47:47 +0100 [thread overview]
Message-ID: <20221209134747.489ccf94@p-imbrenda> (raw)
In-Reply-To: <20221208170502.17984-1-thuth@redhat.com>
On Thu, 8 Dec 2022 18:05:02 +0100
Thomas Huth <thuth@redhat.com> wrote:
> We recently discovered a bug with the time management in nested scenarios
> which got fixed by kernel commit "KVM: s390: vsie: Fix the initialization
> of the epoch extension (epdx) field". This adds a simple test for this
> bug so that it is easier to determine whether the host kernel of a machine
> has already been fixed or not.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> v2: Remove the spurious "2" from the diag 44 opcode
>
> s390x/sie.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/s390x/sie.c b/s390x/sie.c
> index 87575b29..cd3cea10 100644
> --- a/s390x/sie.c
> +++ b/s390x/sie.c
> @@ -58,6 +58,33 @@ static void test_diags(void)
> }
> }
>
> +static void test_epoch_ext(void)
> +{
> + u32 instr[] = {
> + 0xb2780000, /* STCKE 0 */
> + 0x83000044 /* DIAG 0x44 to intercept */
> + };
> +
> + if (!test_facility(139)) {
> + report_skip("epdx: Multiple Epoch Facility is not available");
> + return;
> + }
> +
> + guest[0] = 0x00;
> + memcpy(guest_instr, instr, sizeof(instr));
> +
> + vm.sblk->gpsw.addr = PAGE_SIZE * 2;
> + vm.sblk->gpsw.mask = PSW_MASK_64;
> +
> + vm.sblk->ecd |= ECD_MEF;
> + vm.sblk->epdx = 0x47; /* Setting the epoch extension here ... */
> +
> + sie(&vm);
> +
> + /* ... should result in the same epoch extension here: */
> + report(guest[0] == 0x47, "epdx: different epoch is visible in the guest");
> +}
> +
> static void setup_guest(void)
> {
> setup_vm();
> @@ -80,6 +107,7 @@ int main(void)
>
> setup_guest();
> test_diags();
> + test_epoch_ext();
> sie_guest_destroy(&vm);
>
> done:
next prev parent reply other threads:[~2022-12-09 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 17:05 [kvm-unit-tests v2 PATCH] s390x: sie: Test whether the epoch extension field is working as expected Thomas Huth
2022-12-09 12:47 ` Claudio Imbrenda [this message]
2023-03-24 8:53 ` 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=20221209134747.489ccf94@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=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