public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, david@redhat.com,
	thuth@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 6/8] s390x: css: testing ssch error response
Date: Mon, 29 Mar 2021 09:42:39 +0200	[thread overview]
Message-ID: <dfd959d6-453c-5c06-d0b1-5b657e72c8d4@linux.ibm.com> (raw)
In-Reply-To: <20210326115855.21427c7d@ibm-vm>



On 3/26/21 11:58 AM, Claudio Imbrenda wrote:
> On Fri, 26 Mar 2021 11:41:34 +0100
> Pierre Morel <pmorel@linux.ibm.com> wrote:
> 
>> On 3/25/21 5:02 PM, Claudio Imbrenda wrote:
>>> On Thu, 25 Mar 2021 10:39:05 +0100
>>> Pierre Morel <pmorel@linux.ibm.com> wrote:
>>>    
>>
>> ...snip...
>>
>>
>> Trying to follow your comment, I have some questions:
>>
>>
>>>> +	/* 2- ORB address should be lower than 2G */
>>>> +	report_prefix_push("ORB Address above 2G");
>>>> +	expect_pgm_int();
>>>> +	ssch(test_device_sid, (void *)0x80000000);
>>>
>>> another hardcoded address... you should try allocating memory over
>>> 2G, and try to use it. put a check if there is enough memory, and
>>> skip if you do not have enough memory, like you did below
>>
>> How can I allocate memory above 2G?
> 
> alloc_pages_flags(order, AREA_NORMAL)
> 
> btw that allocation will fail if there is no free memory available
> above 2G
> 
>>>    
>>>> +	check_pgm_int_code(PGM_INT_CODE_ADDRESSING);
>>>> +	report_prefix_pop();
>>>> +
>>>> +	/* 3- ORB address should be available we check 1G*/
>>>> +	top = get_ram_size();
>>>> +	report_prefix_push("ORB Address must be available");
>>>> +	if (top < 0x40000000) {
>>>> +		expect_pgm_int();
>>>> +		ssch(test_device_sid, (void *)0x40000000);
>>>> +		check_pgm_int_code(PGM_INT_CODE_ADDRESSING);
>>>> +	} else {
>>>> +		report_skip("guest started with more than 1G
>>>> memory");
>>>
>>> this is what I meant above. you will need to run this test both
>>> with 1G and with 3G of ram (look at the SCLP test, it has the same
>>> issue)
>>
>> I do not understand, if I test with 3G RAM, I suppose that the
>> framework works right and I have my 3G RAM available.
>> Then I can check with an address under 1G and recheck with an address
>> above 1G.
>>
>> What is the purpose to check with only 1G memory?
> 
> you need to run this test twice, once with 1G and once with 3G.
> it's the same test, so it can't know if it is being run with 1G or
> 3G, so you have to test for it.
> 
> when you need a valid address above 2G, you need to make sure you have
> that much memory, and when you want an invalid address between 1G and
> 2G, you have to make sure you have no more than 1G.

OK, thanks




-- 
Pierre Morel
IBM Lab Boeblingen

  reply	other threads:[~2021-03-29  7:43 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  9:38 [kvm-unit-tests PATCH v2 0/8] Testing SSCH, CSCH and HSCH for errors Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 1/8] s390x: lib: css: disabling a subchannel Pierre Morel
2021-03-25 14:52   ` Claudio Imbrenda
2021-03-25 16:10     ` Pierre Morel
2021-03-26  8:26   ` Janosch Frank
2021-03-26  9:02     ` Pierre Morel
2021-03-29  8:00   ` Thomas Huth
2021-03-29 12:33     ` Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 2/8] s390x: lib: css: SCSW bit definitions Pierre Morel
2021-03-25 15:00   ` Claudio Imbrenda
2021-03-25 16:13     ` Pierre Morel
2021-03-29  8:09   ` Thomas Huth
2021-03-29 12:25     ` Pierre Morel
2021-03-30 11:49   ` Cornelia Huck
2021-03-30 12:59     ` Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 3/8] s390x: css: simplify skipping tests on no device Pierre Morel
2021-03-25 15:21   ` Claudio Imbrenda
2021-03-25 16:21     ` Pierre Morel
2021-03-26  8:41   ` Janosch Frank
2021-03-26  9:04     ` Pierre Morel
2021-03-29  8:19   ` Thomas Huth
2021-03-29 12:39     ` Pierre Morel
2021-03-29 12:50     ` Pierre Morel
2021-03-30 11:52       ` Cornelia Huck
2021-03-30 12:58         ` Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 4/8] s390x: lib: css: separate wait for IRQ and check I/O completion Pierre Morel
2021-03-25 15:24   ` Claudio Imbrenda
2021-03-25 16:23     ` Pierre Morel
2021-03-29  8:21   ` Thomas Huth
2021-03-29 11:00     ` Pierre Morel
2021-03-30 11:57   ` Cornelia Huck
2021-03-30 12:57     ` Pierre Morel
2021-04-01  8:24   ` Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 5/8] s390x: lib: css: add SCSW ctrl expectations to " Pierre Morel
2021-03-25 15:40   ` Claudio Imbrenda
2021-03-29  8:27   ` Thomas Huth
2021-03-29  8:32     ` Thomas Huth
2021-03-29 11:01       ` Pierre Morel
2021-03-29 11:02     ` Pierre Morel
2021-03-30 12:10   ` Cornelia Huck
2021-03-30 12:54     ` Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 6/8] s390x: css: testing ssch error response Pierre Morel
2021-03-25 16:02   ` Claudio Imbrenda
2021-03-25 17:23     ` Pierre Morel
2021-03-26 10:41     ` Pierre Morel
2021-03-26 10:58       ` Claudio Imbrenda
2021-03-29  7:42         ` Pierre Morel [this message]
2021-03-30 13:01           ` Pierre Morel
2021-03-29  9:40   ` Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 7/8] s390x: css: testing halt subchannel Pierre Morel
2021-03-25  9:39 ` [kvm-unit-tests PATCH v2 8/8] s390x: css: testing clear subchannel Pierre Morel

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=dfd959d6-453c-5c06-d0b1-5b657e72c8d4@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@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