From: Steffen Eiden <seiden@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>,
kvm390 mailing list <kvm390-list@tuxmaker.boeblingen.de.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
imbrenda@linux.ibm.com, thuth@redhat.com, nrb@linux.ibm.com,
scgl@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 3/6] s390x: uv-host: Test uv immediate parameter
Date: Tue, 17 May 2022 10:29:31 +0200 [thread overview]
Message-ID: <8c852bcd-6b42-4b54-d3ff-5d63a389b05d@linux.ibm.com> (raw)
In-Reply-To: <20220513095017.16301-4-frankja@linux.ibm.com>
Hey Janosch,
On 5/13/22 11:50, Janosch Frank wrote:
> Let's check if we get a specification PGM exception if we set a
> non-zero i3 when doing a UV call.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> s390x/uv-host.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/s390x/uv-host.c b/s390x/uv-host.c
> index f846fc42..fcb82d24 100644
> --- a/s390x/uv-host.c
> +++ b/s390x/uv-host.c
> @@ -64,6 +64,28 @@ static struct cmd_list cmds[] = {
> { NULL, 0, 0 },
> };
>
> +static void test_i3(void)
> +{
> + struct uv_cb_header uvcb = {
> + .cmd = UVC_CMD_INIT_UV,
> + .len = sizeof(struct uv_cb_init),
> + };
> + unsigned long r1 = 0;
Did you forgot 'r2' or is it missing for a reason?
> + int cc;
> +
> + report_prefix_push("i3");
> + expect_pgm_int();
> + asm volatile(
> + "0: .insn rrf,0xB9A40000,%[r1],%[r2],4,2\n"
> + " ipm %[cc]\n"
> + " srl %[cc],28\n"
> + : [cc] "=d" (cc)
> + : [r1] "a" (r1), [r2] "a" (&uvcb)
> + : "memory", "cc");
> + check_pgm_int_code(PGM_INT_CODE_SPECIFICATION);
> + report_prefix_pop();
> +}
> +
> static void test_priv(void)
> {
> struct uv_cb_header uvcb = {};
> @@ -585,6 +607,7 @@ int main(void)
> goto done;
> }
>
> + test_i3();
> test_priv();
> test_invalid();
> test_uv_uninitialized();
next prev parent reply other threads:[~2022-05-17 8:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:50 [kvm-unit-tests PATCH 0/6] s390x: uv-host: Access check extensions and improvements Janosch Frank
2022-05-13 9:50 ` [kvm-unit-tests PATCH 1/6] s390x: uv-host: Add access checks for donated memory Janosch Frank
2022-05-16 8:21 ` Nico Boehr
2022-05-16 9:22 ` Janosch Frank
2022-05-13 9:50 ` [kvm-unit-tests PATCH 2/6] s390x: uv-host: Add uninitialized UV tests Janosch Frank
2022-05-16 8:37 ` Nico Boehr
2022-05-16 15:02 ` Steffen Eiden
2022-05-16 15:15 ` Janosch Frank
2022-05-16 15:34 ` Steffen Eiden
2022-05-13 9:50 ` [kvm-unit-tests PATCH 3/6] s390x: uv-host: Test uv immediate parameter Janosch Frank
2022-05-17 8:29 ` Steffen Eiden [this message]
2022-05-17 9:03 ` Janosch Frank
2022-05-17 9:04 ` Steffen Eiden
2022-05-13 9:50 ` [kvm-unit-tests PATCH 4/6] s390x: uv-host: Add access exception test Janosch Frank
2022-05-16 8:42 ` Nico Boehr
2022-05-17 8:53 ` Steffen Eiden
2022-05-13 9:50 ` [kvm-unit-tests PATCH 5/6] s390x: uv-host: Add a set secure config parameters test function Janosch Frank
2022-05-17 11:32 ` Steffen Eiden
2022-05-13 9:50 ` [kvm-unit-tests PATCH 6/6] s390x: uv-host: Remove duplicated + Janosch Frank
2022-05-13 15:30 ` Claudio Imbrenda
2022-05-17 11:33 ` Steffen Eiden
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=8c852bcd-6b42-4b54-d3ff-5d63a389b05d@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm390-list@tuxmaker.boeblingen.de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=scgl@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