From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH] s390x: Fix stsi unaligned test and add selector tests
Date: Fri, 20 Sep 2019 09:55:42 +0200 [thread overview]
Message-ID: <fc3a5e82-1099-ef63-fb47-75cdb8109a86@de.ibm.com> (raw)
In-Reply-To: <20190920075020.1698-1-frankja@linux.ibm.com>
On 20.09.19 09:50, Janosch Frank wrote:
> Alignment and selectors test order is not specified and so, if you
> have an unaligned address and invalid selectors it's up to the
> hypervisor to decide which error is presented.
>
> Let's add valid selectors to the unalignmnet test and add selector
> tests.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> s390x/stsi.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/s390x/stsi.c b/s390x/stsi.c
> index 7232cb0..c5bd0a2 100644
> --- a/s390x/stsi.c
> +++ b/s390x/stsi.c
> @@ -35,7 +35,7 @@ static void test_specs(void)
>
> report_prefix_push("unaligned");
> expect_pgm_int();
> - stsi(pagebuf + 42, 1, 0, 0);
> + stsi(pagebuf + 42, 1, 1, 1);
> check_pgm_int_code(PGM_INT_CODE_SPECIFICATION);
> report_prefix_pop();
>
> @@ -71,6 +71,8 @@ static inline unsigned long stsi_get_fc(void *addr)
> static void test_fc(void)
> {
> report("invalid fc", stsi(pagebuf, 7, 0, 0) == 3);
> + report("invalid selector 1", stsi(pagebuf, 1, 0, 1) == 3);
> + report("invalid selector 2", stsi(pagebuf, 1, 1, 0) == 3);
> report("query fc >= 2", stsi_get_fc(pagebuf) >= 2);
> }
>
>
next prev parent reply other threads:[~2019-09-20 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 7:50 [kvm-unit-tests PATCH] s390x: Fix stsi unaligned test and add selector tests Janosch Frank
2019-09-20 7:55 ` Christian Borntraeger [this message]
2019-09-20 8:10 ` David Hildenbrand
2019-09-23 8:10 ` Thomas Huth
2019-09-23 9:48 ` Janosch Frank
2019-09-23 9:59 ` Thomas Huth
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=fc3a5e82-1099-ef63-fb47-75cdb8109a86@de.ibm.com \
--to=borntraeger@de.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