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 09/10] s390x: smp: Add restart when running test
Date: Wed, 29 Apr 2020 10:35:17 -0400 [thread overview]
Message-ID: <20200429143518.1360468-10-frankja@linux.ibm.com> (raw)
In-Reply-To: <20200429143518.1360468-1-frankja@linux.ibm.com>
Let's make sure we can restart a cpu that is already running.
Restarting it if it is stopped is implicitely tested by the the other
restart calls in the smp test.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
---
s390x/smp.c | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/s390x/smp.c b/s390x/smp.c
index bad2131..e6db8f0 100644
--- a/s390x/smp.c
+++ b/s390x/smp.c
@@ -52,6 +52,34 @@ static void test_start(void)
report(1, "start");
}
+/*
+ * Does only test restart when the target is running.
+ * The other tests do restarts when stopped multiple times already.
+ */
+static void test_restart(void)
+{
+ struct cpu *cpu = smp_cpu_from_addr(1);
+ struct lowcore *lc = cpu->lowcore;
+
+ lc->restart_new_psw.mask = extract_psw_mask();
+ lc->restart_new_psw.addr = (unsigned long)test_func;
+
+ /* Make sure cpu is running */
+ smp_cpu_stop(0);
+ set_flag(0);
+ smp_cpu_restart(1);
+ wait_for_flag();
+
+ /*
+ * Wait until cpu 1 has set the flag because it executed the
+ * restart function.
+ */
+ set_flag(0);
+ smp_cpu_restart(1);
+ wait_for_flag();
+ report(1, "restart while running");
+}
+
static void test_stop(void)
{
smp_cpu_stop(1);
@@ -300,6 +328,7 @@ int main(void)
smp_cpu_stop(1);
test_start();
+ test_restart();
test_stop();
test_stop_store_status();
test_store_status();
--
2.25.1
next prev 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 ` [PATCH v3 04/10] s390x: smp: Test local interrupts after cpu reset Janosch Frank
2020-04-29 15:12 ` 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 ` Janosch Frank [this message]
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-10-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox