From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2 4/4] s390x: Test effect of storage keys on diag 308
Date: Tue, 17 May 2022 16:52:53 +0200 [thread overview]
Message-ID: <20220517165253.46799a10@p-imbrenda> (raw)
In-Reply-To: <20220517115607.3252157-5-scgl@linux.ibm.com>
On Tue, 17 May 2022 13:56:07 +0200
Janis Schoetterl-Glausch <scgl@linux.ibm.com> wrote:
> Test that key-controlled protection does not apply to diag 308.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> ---
> s390x/skey.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/s390x/skey.c b/s390x/skey.c
> index 60ae8158..c2d28ffd 100644
> --- a/s390x/skey.c
> +++ b/s390x/skey.c
> @@ -285,6 +285,31 @@ static void test_store_cpu_address(void)
> report_prefix_pop();
> }
>
> +static void test_diag_308(void)
> +{
> + uint16_t response;
> + uint32_t (*ipib)[1024] = (void *)pagebuf;
why not just uint32_t *ipib = (void *)pagebuf; ?
> +
> + report_prefix_push("DIAG 308");
> + (*ipib)[0] = 0; /* Invalid length */
then you can simply do:
ipib[0] = 0;
> + set_storage_key(ipib, 0x28, 0);
> + /* key-controlled protection does not apply */
> + asm volatile (
> + "lr %%r2,%[ipib]\n\t"
> + "spka 0x10\n\t"
> + "diag %%r2,%[code],0x308\n\t"
> + "spka 0\n\t"
> + "lr %[response],%%r3\n"
> + : [response] "=d" (response)
> + : [ipib] "d" (ipib),
> + [code] "d" (5)
> + : "%r2", "%r3"
> + );
> + report(response == 0x402, "no exception on fetch, response: invalid IPIB");
> + set_storage_key(ipib, 0x00, 0);
> + report_prefix_pop();
> +}
> +
> /*
> * Perform CHANNEL SUBSYSTEM CALL (CHSC) instruction while temporarily executing
> * with access key 1.
> @@ -714,6 +739,7 @@ int main(void)
> test_chg();
> test_test_protection();
> test_store_cpu_address();
> + test_diag_308();
> test_channel_subsystem_call();
>
> setup_vm();
next prev parent reply other threads:[~2022-05-17 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 11:56 [kvm-unit-tests PATCH v2 0/4] More skey instr. emulation test Janis Schoetterl-Glausch
2022-05-17 11:56 ` [kvm-unit-tests PATCH v2 1/4] s390x: Fix sclp facility bit numbers Janis Schoetterl-Glausch
2022-05-17 11:56 ` [kvm-unit-tests PATCH v2 2/4] s390x: Test TEID values in storage key test Janis Schoetterl-Glausch
2022-05-17 13:46 ` Claudio Imbrenda
2022-05-17 15:11 ` Janis Schoetterl-Glausch
2022-05-17 15:32 ` Claudio Imbrenda
2022-05-17 11:56 ` [kvm-unit-tests PATCH v2 3/4] s390x: Test effect of storage keys on some more instructions Janis Schoetterl-Glausch
2022-05-17 13:54 ` Claudio Imbrenda
2022-05-17 15:34 ` Janis Schoetterl-Glausch
2022-05-17 11:56 ` [kvm-unit-tests PATCH v2 4/4] s390x: Test effect of storage keys on diag 308 Janis Schoetterl-Glausch
2022-05-17 14:52 ` Claudio Imbrenda [this message]
2022-05-17 15:47 ` Janis Schoetterl-Glausch
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=20220517165253.46799a10@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=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