From: David Hildenbrand <david@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org,
borntraeger@de.ibm.com, cohuck@redhat.com
Subject: Re: [PATCH v2 08/10] s390x: smp: Wait for sigp completion
Date: Fri, 24 Apr 2020 12:11:36 +0200 [thread overview]
Message-ID: <6084d368-86d6-b8fd-d4d3-5e0d72cef590@redhat.com> (raw)
In-Reply-To: <20200423091013.11587-9-frankja@linux.ibm.com>
On 23.04.20 11:10, Janosch Frank wrote:
> Sigp orders are not necessarily finished when the processor finished
> the sigp instruction. We need to poll if the order has been finished
> before we continue.
>
> For (re)start and stop we already use sigp sense running and sigp
> sense loops. But we still lack completion checks for stop and store
> status, as well as the cpu resets.
>
> Let's add them.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> ---
> lib/s390x/smp.c | 8 ++++++++
> lib/s390x/smp.h | 1 +
> s390x/smp.c | 4 ++++
> 3 files changed, 13 insertions(+)
>
> diff --git a/lib/s390x/smp.c b/lib/s390x/smp.c
> index 6ef0335..2555bf4 100644
> --- a/lib/s390x/smp.c
> +++ b/lib/s390x/smp.c
> @@ -154,6 +154,14 @@ int smp_cpu_start(uint16_t addr, struct psw psw)
> return rc;
> }
>
> +void smp_cpu_wait_for_completion(uint16_t addr)
> +{
> + uint32_t status;
> +
> + /* Loops when cc == 2, i.e. when the cpu is busy with a sigp order */
> + sigp_retry(1, SIGP_SENSE, 0, &status);
> +}
> +
> int smp_cpu_destroy(uint16_t addr)
> {
> struct cpu *cpu;
> diff --git a/lib/s390x/smp.h b/lib/s390x/smp.h
> index ce63a89..a8b98c0 100644
> --- a/lib/s390x/smp.h
> +++ b/lib/s390x/smp.h
> @@ -45,6 +45,7 @@ int smp_cpu_restart(uint16_t addr);
> int smp_cpu_start(uint16_t addr, struct psw psw);
> int smp_cpu_stop(uint16_t addr);
> int smp_cpu_stop_store_status(uint16_t addr);
> +void smp_cpu_wait_for_completion(uint16_t addr);
> int smp_cpu_destroy(uint16_t addr);
> int smp_cpu_setup(uint16_t addr, struct psw psw);
> void smp_teardown(void);
> diff --git a/s390x/smp.c b/s390x/smp.c
> index 7462211..48321f4 100644
> --- a/s390x/smp.c
> +++ b/s390x/smp.c
> @@ -75,6 +75,7 @@ static void test_stop_store_status(void)
> lc->prefix_sa = 0;
> lc->grs_sa[15] = 0;
> smp_cpu_stop_store_status(1);
> + smp_cpu_wait_for_completion(1);
> mb();
> report(lc->prefix_sa == (uint32_t)(uintptr_t)cpu->lowcore, "prefix");
> report(lc->grs_sa[15], "stack");
> @@ -85,6 +86,7 @@ static void test_stop_store_status(void)
> lc->prefix_sa = 0;
> lc->grs_sa[15] = 0;
> smp_cpu_stop_store_status(1);
Just curious: Would it make sense to add that inside
smp_cpu_stop_store_status() instead?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-04-24 10:11 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 ` [PATCH v2 06/10] s390x: smp: Remove unneeded cpu loops Janosch Frank
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 [this message]
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=6084d368-86d6-b8fd-d4d3-5e0d72cef590@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox