From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, rkrcmar@redhat.com
Subject: [PATCH kvm-unit-tests 0/3] arm/arm64: introduce on_cpu[_async]
Date: Thu, 1 Jun 2017 15:49:59 +0200 [thread overview]
Message-ID: <20170601135002.26704-1-drjones@redhat.com> (raw)
and smp_run becomes on_cpus, which can be run more than once.
Andrew Jones (3):
arm/arm64: smp: rename secondary_halt to do_idle
arm/arm64: smp: introduce on_cpu and on_cpu_async
arm/arm64: rename smp_run to on_cpus
arm/cstart.S | 2 +-
arm/cstart64.S | 2 +-
arm/gic.c | 2 +-
arm/selftest.c | 2 +-
arm/spinlock-test.c | 2 +-
lib/arm/asm/smp.h | 16 ++++++++--
lib/arm/smp.c | 87 +++++++++++++++++++++++++++++++++++++++++++----------
7 files changed, 90 insertions(+), 23 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-01 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 13:49 Andrew Jones [this message]
2017-06-01 13:50 ` [PATCH kvm-unit-tests 1/3] arm/arm64: smp: rename secondary_halt to do_idle Andrew Jones
2017-06-01 13:50 ` [PATCH kvm-unit-tests 2/3] arm/arm64: smp: introduce on_cpu and on_cpu_async Andrew Jones
2017-06-01 13:50 ` [PATCH kvm-unit-tests 3/3] arm/arm64: rename smp_run to on_cpus 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=20170601135002.26704-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).