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 v2 06/10] s390x: smp: Remove unneeded cpu loops
Date: Thu, 23 Apr 2020 05:10:09 -0400 [thread overview]
Message-ID: <20200423091013.11587-7-frankja@linux.ibm.com> (raw)
In-Reply-To: <20200423091013.11587-1-frankja@linux.ibm.com>
Now that we have a loop which is executed after we return from the
main function of a secondary cpu, we can remove the surplus loops.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: David Hildenbrand <david@redhat.com>
---
s390x/smp.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/s390x/smp.c b/s390x/smp.c
index a8e3dd7..7462211 100644
--- a/s390x/smp.c
+++ b/s390x/smp.c
@@ -35,15 +35,9 @@ static void set_flag(int val)
mb();
}
-static void cpu_loop(void)
-{
- for (;;) {}
-}
-
static void test_func(void)
{
set_flag(1);
- cpu_loop();
}
static void test_start(void)
@@ -292,7 +286,7 @@ int main(void)
/* Setting up the cpu to give it a stack and lowcore */
psw.mask = extract_psw_mask();
- psw.addr = (unsigned long)cpu_loop;
+ psw.addr = (unsigned long)test_func;
smp_cpu_setup(1, psw);
smp_cpu_stop(1);
--
2.25.1
next prev parent reply other threads:[~2020-04-23 9:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 9:10 [PATCH v2 00/10] s390x: smp: Improve smp code part 2 Janosch Frank
2020-04-23 9:10 ` [PATCH v2 01/10] s390x: smp: Test all CRs on initial reset Janosch Frank
2020-04-23 15:39 ` David Hildenbrand
2020-04-24 9:33 ` [PATCH v3] " Janosch Frank
2020-04-24 10:03 ` David Hildenbrand
2020-04-23 9:10 ` [PATCH v2 02/10] s390x: smp: Dirty fpc before initial reset test Janosch Frank
2020-04-23 9:10 ` [PATCH v2 03/10] s390x: smp: Test stop and store status on a running and stopped cpu Janosch Frank
2020-04-23 16:03 ` David Hildenbrand
2020-04-23 9:10 ` [PATCH v2 04/10] s390x: smp: Test local interrupts after cpu reset Janosch Frank
2020-04-24 10:07 ` David Hildenbrand
2020-04-24 11:51 ` Janosch Frank
2020-04-23 9:10 ` [PATCH v2 05/10] s390x: smp: Loop if secondary cpu returns into cpu setup again Janosch Frank
2020-04-24 10:08 ` David Hildenbrand
2020-04-23 9:10 ` Janosch Frank [this message]
2020-04-23 9:10 ` [PATCH v2 07/10] s390x: smp: Use full PSW to bringup new cpu Janosch Frank
2020-04-24 10:09 ` David Hildenbrand
2020-04-24 11:16 ` Janosch Frank
2020-04-24 11:23 ` David Hildenbrand
2020-04-24 11:31 ` Janosch Frank
2020-04-23 9:10 ` [PATCH v2 08/10] s390x: smp: Wait for sigp completion Janosch Frank
2020-04-24 10:11 ` David Hildenbrand
2020-04-24 11:40 ` Janosch Frank
2020-04-29 8:57 ` Janosch Frank
2020-04-29 9:06 ` David Hildenbrand
2020-04-29 9:37 ` Janosch Frank
2020-04-29 9:55 ` David Hildenbrand
2020-04-29 11:21 ` Janosch Frank
2020-04-29 11:47 ` David Hildenbrand
2020-04-29 12:09 ` Janosch Frank
2020-04-29 12:15 ` David Hildenbrand
2020-04-23 9:10 ` [PATCH v2 09/10] s390x: smp: Add restart when running test Janosch Frank
2020-04-24 10:13 ` David Hildenbrand
2020-04-23 9:10 ` [PATCH v2 10/10] s390x: Fix library constant definitions Janosch Frank
2020-04-24 10:13 ` 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=20200423091013.11587-7-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