From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, rkrcmar@redhat.com
Subject: [PATCH kvm-unit-tests 0/2] arm/arm64: smp: on_cpu improvements
Date: Fri, 2 Jun 2017 17:12:50 +0200 [thread overview]
Message-ID: <20170602151252.32338-1-drjones@redhat.com> (raw)
After posting on_cpu() support yesterday I thought of some potential
issues.
1) cpu0 was the only cpu allowed to call on_cpus, and no cpu was
allowed to call on_cpu on cpu0 (as it'll never idle).
2) deadlocks are easy with this idle state scheduling model, but
also easy to detect, so we should.
Andrew Jones (2):
arm/arm64: smp: cpu0 is special
arm/arm64: smp: add deadlock detection
lib/arm/asm/smp.h | 2 ++
lib/arm/smp.c | 47 +++++++++++++++++++++++++++++++++++++----------
2 files changed, 39 insertions(+), 10 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-02 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:12 Andrew Jones [this message]
2017-06-02 15:12 ` [PATCH kvm-unit-tests 1/2] arm/arm64: smp: cpu0 is special Andrew Jones
2017-06-02 15:12 ` [PATCH kvm-unit-tests 2/2] arm/arm64: smp: add deadlock detection Andrew Jones
2017-06-02 15:26 ` Andrew Jones
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=20170602151252.32338-1-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).