From: Nicholas Piggin <npiggin@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Alexander Graf <agraf@suse.com>,
kvm-ppc@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/3] KVM: PPC: Book3S: 64-bit CONFIG_RELOCATABLE fixes
Date: Thu, 1 Dec 2016 18:18:09 +1100 [thread overview]
Message-ID: <20161201071812.23258-1-npiggin@gmail.com> (raw)
Hi,
I didn't get any objections to the approach proposed in my
earlier RFC, so I've gone ahead with R12 = (CR | trap #) approach.
It avoided an extra register save with HV and the PR handler ended
up not being too bad.
This passed KVM boot testing with 64-bit HV and PR, with the (host)
kernel running at non-0. Without these patches, the same configuration
crashes immediately.
Thanks,
Nick
Nicholas Piggin (3):
KVM: PPC: Book3S: Change interrupt call to reduce scratch space use on
HV
KVM: PPC: Book3S: Move 64-bit KVM interrupt handler out from alt
section
KVM: PPC: Book3S: 64-bit CONFIG_RELOCATABLE support for interrupts
arch/powerpc/include/asm/exception-64s.h | 67 +++++++++++++++++++++++++-------
arch/powerpc/include/asm/head-64.h | 2 +-
arch/powerpc/kernel/exceptions-64s.S | 10 ++---
arch/powerpc/kvm/book3s_hv_rmhandlers.S | 19 +++++----
arch/powerpc/kvm/book3s_segment.S | 32 +++++++++++----
5 files changed, 94 insertions(+), 36 deletions(-)
--
2.10.2
next reply other threads:[~2016-12-01 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 7:18 Nicholas Piggin [this message]
2016-12-01 7:18 ` [PATCH 1/3] KVM: PPC: Book3S: Change interrupt call to reduce scratch space use on HV Nicholas Piggin
2016-12-06 6:09 ` Paul Mackerras
2016-12-06 8:31 ` Nicholas Piggin
2016-12-01 7:18 ` [PATCH 2/3] KVM: PPC: Book3S: Move 64-bit KVM interrupt handler out from alt section Nicholas Piggin
2016-12-01 7:18 ` [PATCH 3/3] KVM: PPC: Book3S: 64-bit CONFIG_RELOCATABLE support for interrupts 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=20161201071812.23258-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=agraf@suse.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).