All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH 01/10] s390x: smp: Test all CRs on initial reset
Date: Tue, 24 Mar 2020 11:09:25 +0100	[thread overview]
Message-ID: <5be194c7-924d-df25-2c21-f5d3195236b3@de.ibm.com> (raw)
In-Reply-To: <c1f01ea5-219e-4680-72bd-56f68270bf9b@linux.ibm.com>



On 24.03.20 11:08, Janosch Frank wrote:
> On 3/24/20 10:52 AM, Christian Borntraeger wrote:
>>
>>
>> On 24.03.20 09:12, Janosch Frank wrote:
>>> All CRs are set to 0 and CRs 0 and 14 are set to pre-defined values,
>>> so we also need to test 1-13 and 15 for 0.
>>>
>>> And while we're at it, let's also set some values to cr 1, 7 and 13, so
>>> we can actually be sure that they will be zeroed.
>>>
>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>>> ---
>>>  s390x/smp.c | 16 +++++++++++++++-
>>>  1 file changed, 15 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/s390x/smp.c b/s390x/smp.c
>>> index fa40753524f321d4..8c9b98aabd9e8222 100644
>>> --- a/s390x/smp.c
>>> +++ b/s390x/smp.c
>>> @@ -182,16 +182,28 @@ static void test_emcall(void)
>>>  	report_prefix_pop();
>>>  }
>>>
>>> +/* Used to dirty registers of cpu #1 before it is reset */
>>> +static void test_func_initial(void)
>>> +{
>>> +	lctlg(1, 0x42000UL);
>>> +	lctlg(7, 0x43000UL);
>>> +	lctlg(13, 0x44000UL);
>>> +	set_flag(1);
>>> +}
>>> +
>>>  static void test_reset_initial(void)
>>>  {
>>>  	struct cpu_status *status = alloc_pages(0);
>>> +	uint64_t nullp[12] = {};
>>>  	struct psw psw;
>>>
>>>  	psw.mask = extract_psw_mask();
>>> -	psw.addr = (unsigned long)test_func;
>>> +	psw.addr = (unsigned long)test_func_initial;
>>>
>>>  	report_prefix_push("reset initial");
>>> +	set_flag(0);
>>>  	smp_cpu_start(1, psw);
>>> +	wait_for_flag();
>>>
>>>  	sigp_retry(1, SIGP_INITIAL_CPU_RESET, 0, NULL);
>>>  	sigp(1, SIGP_STORE_STATUS_AT_ADDRESS, (uintptr_t)status, NULL);
>>> @@ -202,6 +214,8 @@ static void test_reset_initial(void)
>>>  	report(!status->fpc, "fpc");
>>>  	report(!status->cputm, "cpu timer");
>>>  	report(!status->todpr, "todpr");
>>> +	report(!memcmp(&status->crs[1], nullp, sizeof(status->crs[1]) * 12), "cr1-13 == 0");
>>> +	report(status->crs[15] == 0, "cr15 == 0");
>>>  	report_prefix_pop();
>>
>> Why not add a check for crs[0] == 0xe0 
>> and crs[14] = 0xc2000000
> 
> You mean the checks which are done a few lines below this?
> This patch just actually dirties registers which should be set to 0 so
> we can really be sure that they have been touched.

Right. So feel free to add my RB. 

  reply	other threads:[~2020-03-24 10:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24  8:12 [kvm-unit-tests PATCH 00/10] s390x: smp: Improve smp code part 2 Janosch Frank
2020-03-24  8:12 ` [kvm-unit-tests PATCH 01/10] s390x: smp: Test all CRs on initial reset Janosch Frank
2020-03-24  9:52   ` Christian Borntraeger
2020-03-24 10:05     ` Christian Borntraeger
2020-03-24 10:08     ` Janosch Frank
2020-03-24 10:09       ` Christian Borntraeger [this message]
2020-03-24  8:12 ` [kvm-unit-tests PATCH 02/10] s390x: smp: Dirty fpc before initial reset test Janosch Frank
2020-03-24  8:12 ` [kvm-unit-tests PATCH 03/10] s390x: smp: Test stop and store status on a running and stopped cpu Janosch Frank
2020-03-24 12:04   ` Cornelia Huck
2020-03-24  8:12 ` [kvm-unit-tests PATCH 04/10] s390x: smp: Test local interrupts after cpu reset Janosch Frank
2020-03-24 12:06   ` Cornelia Huck
2020-03-31  9:07   ` David Hildenbrand
2020-03-31  9:28     ` Janosch Frank
2020-03-31 17:27       ` David Hildenbrand
2020-04-01  7:19         ` Janosch Frank
2020-04-06  9:27           ` David Hildenbrand
2020-03-24  8:12 ` [kvm-unit-tests PATCH 05/10] s390x: smp: Loop if secondary cpu returns into cpu setup again Janosch Frank
2020-03-24 12:21   ` Cornelia Huck
2020-03-24  8:12 ` [kvm-unit-tests PATCH 06/10] s390x: smp: Remove unneeded cpu loops Janosch Frank
2020-03-24  8:12 ` [kvm-unit-tests PATCH 07/10] s390x: smp: Use full PSW to bringup new cpu Janosch Frank
2020-03-24 12:26   ` Cornelia Huck
2020-03-24  8:12 ` [kvm-unit-tests PATCH 08/10] s390x: smp: Wait for sigp completion Janosch Frank
2020-03-24 12:38   ` Cornelia Huck
2020-03-31  9:10   ` David Hildenbrand
2020-03-24  8:12 ` [kvm-unit-tests PATCH 09/10] s390x: smp: Add restart when running test Janosch Frank
2020-03-24 12:45   ` Cornelia Huck
2020-03-31  9:12   ` David Hildenbrand
2020-03-24  8:12 ` [kvm-unit-tests PATCH 10/10] s390x: Fix library constant definitions Janosch Frank
2020-03-24 11:06   ` Christian Borntraeger
2020-03-24 12:24   ` Cornelia Huck

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=5be194c7-924d-df25-2c21-f5d3195236b3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.