From: Thomas Huth <thuth@redhat.com>
To: Nico Boehr <nrb@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v1 3/3] s390x: add pgm spec interrupt loop test
Date: Thu, 30 Jun 2022 19:25:57 +0200 [thread overview]
Message-ID: <069be6f0-2f3a-3fea-3eca-d42f99e98220@redhat.com> (raw)
In-Reply-To: <20220630113059.229221-4-nrb@linux.ibm.com>
On 30/06/2022 13.30, Nico Boehr wrote:
> An invalid PSW causes a program interrupt. When an invalid PSW is
> introduced in the pgm_new_psw, an interrupt loop occurs as soon as a
> program interrupt is caused.
>
> QEMU should detect that and panick the guest, hence add a test for it.
>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> ---
....
> +int main(void)
> +{
> + report_prefix_push("pgmint-loop");
> +
> + lowcore.pgm_new_psw.addr = (uint64_t) pgm_int_handler;
> + /* bit 12 set is invalid */
> + lowcore.pgm_new_psw.mask = extract_psw_mask() | BIT(63 - 12);
Basically patch looks fine to me ... just an idea for an extension (but that
could also be done later):
Looking at the is_valid_psw() function in the Linux kernel sources, there
are a couple of additional condition that could cause a PGM interrupt loop
... you could maybe check them here, too, e.g. by adding a "extra_params =
-append '...'" in the unittests.cfg file to select the indiviual tests via
argv[] ?
Thomas
next prev parent reply other threads:[~2022-06-30 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:30 [kvm-unit-tests PATCH v1 0/3] Add panic test support Nico Boehr
2022-06-30 11:30 ` [kvm-unit-tests PATCH v1 1/3] runtime: add support for panic tests Nico Boehr
2022-06-30 17:49 ` Thomas Huth
2022-06-30 11:30 ` [kvm-unit-tests PATCH v1 2/3] s390x: add extint loop test Nico Boehr
2022-06-30 17:55 ` Thomas Huth
2022-07-04 8:32 ` Janosch Frank
2022-06-30 11:30 ` [kvm-unit-tests PATCH v1 3/3] s390x: add pgm spec interrupt " Nico Boehr
2022-06-30 14:38 ` Janis Schoetterl-Glausch
2022-06-30 17:11 ` Thomas Huth
2022-07-01 10:49 ` Janis Schoetterl-Glausch
2022-06-30 17:25 ` Thomas Huth [this message]
2022-07-04 9:06 ` Janosch Frank
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=069be6f0-2f3a-3fea-3eca-d42f99e98220@redhat.com \
--to=thuth@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 \
/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