All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org, david@redhat.com,
	borntraeger@de.ibm.com, cohuck@redhat.com
Subject: [PATCH v3 04/10] s390x: smp: Test local interrupts after cpu reset
Date: Wed, 29 Apr 2020 10:35:12 -0400	[thread overview]
Message-ID: <20200429143518.1360468-5-frankja@linux.ibm.com> (raw)
In-Reply-To: <20200429143518.1360468-1-frankja@linux.ibm.com>

Local interrupts (external and emergency call) should be cleared after
any cpu reset.

Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---
 s390x/smp.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/s390x/smp.c b/s390x/smp.c
index 4c50183..5e2e517 100644
--- a/s390x/smp.c
+++ b/s390x/smp.c
@@ -245,6 +245,19 @@ static void test_reset_initial(void)
 	report_prefix_pop();
 }
 
+static void test_local_ints(void)
+{
+	unsigned long mask;
+
+	/* 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;
@@ -253,10 +266,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");
 	report_prefix_pop();
 }
 
-- 
2.25.1

  parent reply	other threads:[~2020-04-29 14:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 14:35 [PATCH v3 00/10] s390x: smp: Improve smp code part 2 Janosch Frank
2020-04-29 14:35 ` [PATCH v3 01/10] s390x: smp: Test all CRs on initial reset Janosch Frank
2020-04-29 14:35 ` [PATCH v3 02/10] s390x: smp: Dirty fpc before initial reset test Janosch Frank
2020-04-29 14:35 ` [PATCH v3 03/10] s390x: smp: Test stop and store status on a running and stopped cpu Janosch Frank
2020-04-29 14:35 ` Janosch Frank [this message]
2020-04-29 15:12   ` [PATCH v3 04/10] s390x: smp: Test local interrupts after cpu reset David Hildenbrand
2020-04-29 14:35 ` [PATCH v3 05/10] s390x: smp: Loop if secondary cpu returns into cpu setup again Janosch Frank
2020-04-29 15:12   ` David Hildenbrand
2020-04-29 14:35 ` [PATCH v3 06/10] s390x: smp: Remove unneeded cpu loops Janosch Frank
2020-04-29 14:35 ` [PATCH v3 07/10] s390x: smp: Use full PSW to bringup new cpu Janosch Frank
2020-04-29 14:35 ` [PATCH v3 08/10] s390x: smp: Wait for sigp completion Janosch Frank
2020-04-29 15:15   ` David Hildenbrand
2020-04-30  7:40     ` Janosch Frank
2020-04-30  7:42       ` David Hildenbrand
2020-04-29 14:35 ` [PATCH v3 09/10] s390x: smp: Add restart when running test Janosch Frank
2020-04-29 14:35 ` [PATCH v3 10/10] s390x: Fix library constant definitions Janosch Frank
2020-04-30 15:00 ` [PATCH v3 00/10] s390x: smp: Improve smp code part 2 David Hildenbrand

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=20200429143518.1360468-5-frankja@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.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.