From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 1/6] s390x: uv-guest: Add invalid share location test
Date: Tue, 20 Apr 2021 10:48:49 +0200 [thread overview]
Message-ID: <3366db5a-d3ce-85c0-9e0d-a35144b5c6c9@redhat.com> (raw)
In-Reply-To: <92c5e657-a483-eeb4-5902-651be2cd5356@linux.ibm.com>
On 19/04/2021 13.45, Janosch Frank wrote:
> On 4/19/21 1:24 PM, Thomas Huth wrote:
>> On 16/03/2021 10.16, Janosch Frank wrote:
>>> Let's also test sharing unavailable memory.
>>>
>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>> ---
>>> s390x/uv-guest.c | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/s390x/uv-guest.c b/s390x/uv-guest.c
>>> index 99544442..a13669ab 100644
>>> --- a/s390x/uv-guest.c
>>> +++ b/s390x/uv-guest.c
>>> @@ -15,6 +15,7 @@
>>> #include <asm/interrupt.h>
>>> #include <asm/facility.h>
>>> #include <asm/uv.h>
>>> +#include <sclp.h>
>>>
>>> static unsigned long page;
>>>
>>> @@ -99,6 +100,10 @@ static void test_sharing(void)
>>> uvcb.header.len = sizeof(uvcb);
>>> cc = uv_call(0, (u64)&uvcb);
>>> report(cc == 0 && uvcb.header.rc == UVC_RC_EXECUTED, "share");
>>> + uvcb.paddr = get_ram_size() + PAGE_SIZE;
>>> + cc = uv_call(0, (u64)&uvcb);
>>> + report(cc == 1 && uvcb.header.rc == 0x101, "invalid memory");
>>
>> Would it make sense to add a #define for 0x101 ?
>>
>
> The RCs change meaning with each UV call so we can only re-use a small
> number of constants which wouldn't gain us a lot.
Ok, fair point. A define just for one spot does not make too much sense, indeed.
Thomas
next prev parent reply other threads:[~2021-04-20 8:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9:16 [kvm-unit-tests PATCH 0/6] s390x: uv: Extend guest test and add host test Janosch Frank
2021-03-16 9:16 ` [kvm-unit-tests PATCH 1/6] s390x: uv-guest: Add invalid share location test Janosch Frank
2021-04-19 11:24 ` Thomas Huth
2021-04-19 11:45 ` Janosch Frank
2021-04-20 8:48 ` Thomas Huth [this message]
2021-04-20 13:40 ` Claudio Imbrenda
2021-04-21 11:04 ` Cornelia Huck
2021-03-16 9:16 ` [kvm-unit-tests PATCH 2/6] s390x: Add more Ultravisor command structure definitions Janosch Frank
2021-04-20 14:09 ` Claudio Imbrenda
2021-04-21 11:13 ` Cornelia Huck
2021-04-26 14:33 ` Janosch Frank
2021-03-16 9:16 ` [kvm-unit-tests PATCH 3/6] s390x: uv: Add UV lib Janosch Frank
2021-04-20 14:15 ` Claudio Imbrenda
2021-04-26 14:20 ` Janosch Frank
2021-03-16 9:16 ` [kvm-unit-tests PATCH 4/6] s390x: Test for share/unshare call support before using them Janosch Frank
2021-04-20 14:18 ` Claudio Imbrenda
2021-03-16 9:16 ` [kvm-unit-tests PATCH 5/6] s390x: uv-guest: Test invalid commands Janosch Frank
2021-04-20 14:26 ` Claudio Imbrenda
2021-04-26 13:40 ` Janosch Frank
2021-03-16 9:16 ` [kvm-unit-tests PATCH 6/6] s390x: Add UV host test Janosch Frank
2021-04-20 15:47 ` Claudio Imbrenda
2021-04-26 14:31 ` Janosch Frank
2021-04-19 7:24 ` [kvm-unit-tests PATCH 0/6] s390x: uv: Extend guest test and add " 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=3366db5a-d3ce-85c0-9e0d-a35144b5c6c9@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).