All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 04/10] s390x: smp: Test local interrupts after cpu reset
Date: Wed, 1 Apr 2020 09:19:55 +0200	[thread overview]
Message-ID: <9c11caa4-04ff-7cc9-8f62-371d2d200048@linux.ibm.com> (raw)
In-Reply-To: <3631ad95-6920-1089-6e87-8687c9f100b6@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 2584 bytes --]

On 3/31/20 7:27 PM, David Hildenbrand wrote:
> On 31.03.20 11:28, Janosch Frank wrote:
>> On 3/31/20 11:07 AM, David Hildenbrand wrote:
>>> On 24.03.20 09:12, Janosch Frank wrote:
>>>> Local interrupts (external and emergency call) should be cleared after
>>>> any cpu reset.
>>>>
>>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>>> ---
>>>>  s390x/smp.c | 22 ++++++++++++++++++++++
>>>>  1 file changed, 22 insertions(+)
>>>>
>>>> diff --git a/s390x/smp.c b/s390x/smp.c
>>>> index 8a6cd1d8b17d76c6..a8e3dd7aac0c788c 100644
>>>> --- a/s390x/smp.c
>>>> +++ b/s390x/smp.c
>>>> @@ -243,6 +243,20 @@ static void test_reset_initial(void)
>>>>  	report_prefix_pop();
>>>>  }
>>>>  
>>>> +static void test_local_ints(void)
>>>> +{
>>>> +	unsigned long mask;
>>>> +
>>>> +	expect_ext_int();
>>>> +	/* Open masks for ecall and emcall */
>>>> +	ctl_set_bit(0, 13);
>>>> +	ctl_set_bit(0, 14);
>>>> +	mask = extract_psw_mask();
>>>> +	mask |= PSW_MASK_EXT;
>>>> +	load_psw_mask(mask);
>>>> +	set_flag(1);
>>>> +}
>>>> +
>>>>  static void test_reset(void)
>>>>  {
>>>>  	struct psw psw;
>>>> @@ -251,10 +265,18 @@ static void test_reset(void)
>>>>  	psw.addr = (unsigned long)test_func;
>>>>  
>>>>  	report_prefix_push("cpu reset");
>>>> +	sigp(1, SIGP_EMERGENCY_SIGNAL, 0, NULL);
>>>> +	sigp(1, SIGP_EXTERNAL_CALL, 0, NULL);
>>>>  	smp_cpu_start(1, psw);
>>>>  
>>>>  	sigp_retry(1, SIGP_CPU_RESET, 0, NULL);
>>>>  	report(smp_cpu_stopped(1), "cpu stopped");
>>>> +
>>>> +	set_flag(0);
>>>> +	psw.addr = (unsigned long)test_local_ints;
>>>> +	smp_cpu_start(1, psw);
>>>> +	wait_for_flag();
>>>> +	report(true, "local interrupts cleared");
>>>
>>>
>>> How can you be sure they were actually cleared/delivered?
>>>
>> Because cpu 1 would get a ext int it didn't expect and would do a
>> report_abort() as pecified in lib/s390x/interrupt.c
> 
> But what if it *didn't* get the interrupts delivered.

Well, the target is still looping until the reset initial test is
executed and from personal experience I can say that this test bites
rather fast.

We could execute an instruction with a mandatory exit which will prompt
KVM to inject any remaining IRQs before setting the flag to 1.

Unfortunately we do not have a polling instruction for non-IO interrupts
at the moment to verify this test.

> 
> Then cpu 1 will simply (test_local_ints()) unlock interrupts, load the
> psw mask, set the flag and be done with it. What am I missing? How can
> you be sure the interrupts on cpu 1 were actually delivered?
>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-04-01  7:20 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
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 [this message]
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=9c11caa4-04ff-7cc9-8f62-371d2d200048@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=david@redhat.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.