From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Gautham R . Shenoy" <ego@linux.vnet.ibm.com>,
kvm-ppc@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v10 0/2] powerpc/64s: reimplement book3s idle code in C
Date: Sun, 28 Apr 2019 21:45:13 +1000 [thread overview]
Message-ID: <20190428114515.32683-1-npiggin@gmail.com> (raw)
The KVM code is in better shape now, survives various testing I came
up with, so should be ready for more review.
I won't post it again with the KVM part split out unless significant
changes are required there. As explained in the comments for patch 1,
the split results in some intermediate KVM issues, but the split is
supposed to make KVM review easier.
Gautham I left your review tag, quite a lot of KVM changes since he
reviewed it, but non-KVM patch is not much different. Let me know if
I should drop it.
Thanks,
Nick
Nicholas Piggin (2):
powerpc/64s: reimplement book3s idle code in C
powerpc/64s: KVM update for reimplement book3s idle code in C
arch/powerpc/include/asm/cpuidle.h | 19 +-
arch/powerpc/include/asm/paca.h | 40 +-
arch/powerpc/include/asm/processor.h | 9 +-
arch/powerpc/include/asm/reg.h | 8 +-
arch/powerpc/kernel/asm-offsets.c | 18 -
arch/powerpc/kernel/exceptions-64s.S | 23 +-
arch/powerpc/kernel/idle_book3s.S | 1099 +++-------------------
arch/powerpc/kernel/setup-common.c | 4 +-
arch/powerpc/kvm/book3s_hv_rmhandlers.S | 118 ++-
arch/powerpc/platforms/powernv/idle.c | 902 ++++++++++++++----
arch/powerpc/platforms/powernv/subcore.c | 2 +-
arch/powerpc/xmon/xmon.c | 24 +-
12 files changed, 1009 insertions(+), 1257 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-28 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 11:45 Nicholas Piggin [this message]
2019-04-28 11:45 ` [PATCH v10 1/2] powerpc/64s: reimplement book3s idle code in C Nicholas Piggin
2019-04-28 11:45 ` [PATCH v10 2/2] powerpc/64s: KVM update for " Nicholas Piggin
2019-05-13 6:42 ` Paul Mackerras
2019-05-16 4:43 ` Nicholas Piggin
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=20190428114515.32683-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=ego@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).