From: Thomas Huth <thuth@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: david@redhat.com, Janosch Frank <frankja@linux.ibm.com>
Subject: [kvm-unit-tests PULL 3/9] s390x: Stop the cpu that is executing exit()
Date: Tue, 4 Feb 2020 08:13:29 +0100 [thread overview]
Message-ID: <20200204071335.18180-4-thuth@redhat.com> (raw)
In-Reply-To: <20200204071335.18180-1-thuth@redhat.com>
From: Janosch Frank <frankja@linux.ibm.com>
CPU 0 is not necessarily the CPU which does the exit if we ran into a
test abort situation. So, let's ask stap() which cpu does the exit and
stop it on exit.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Message-Id: <20200201152851.82867-4-frankja@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
lib/s390x/io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/s390x/io.c b/lib/s390x/io.c
index 32f09b5..e091c37 100644
--- a/lib/s390x/io.c
+++ b/lib/s390x/io.c
@@ -46,6 +46,6 @@ void exit(int code)
smp_teardown();
printf("\nEXIT: STATUS=%d\n", ((code) << 1) | 1);
while (1) {
- sigp(0, SIGP_STOP, 0, NULL);
+ sigp(stap(), SIGP_STOP, 0, NULL);
}
}
--
2.18.1
next prev parent reply other threads:[~2020-02-04 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 7:13 [kvm-unit-tests PULL 0/9] s390x and CI patches Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 1/9] s390x: smp: Cleanup smp.c Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 2/9] s390x: smp: Fix ecall and emcall report strings Thomas Huth
2020-02-04 7:13 ` Thomas Huth [this message]
2020-02-04 7:13 ` [kvm-unit-tests PULL 4/9] s390x: Add cpu id to interrupt error prints Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 5/9] s390x: smp: Only use smp_cpu_setup once Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 6/9] s390x: smp: Rework cpu start and active tracking Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 7/9] s390x: smp: Wait for cpu setup to finish Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 8/9] gitlab-ci.yml: Remove ioapic from the x86 tests Thomas Huth
2020-02-04 7:13 ` [kvm-unit-tests PULL 9/9] travis.yml: Prevent 'script' from premature exit Thomas Huth
2020-02-05 14:58 ` [kvm-unit-tests PULL 0/9] s390x and CI patches Paolo Bonzini
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=20200204071335.18180-4-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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