From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: "Shreyas B . Prabhu" <shreyas@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
"Gautham R . Shenoy" <ego@linux.vnet.ibm.com>
Subject: Re: powerpc/64s: relocation, register save fixes for system reset interrupt
Date: Thu, 27 Oct 2016 22:38:54 +1100 (AEDT) [thread overview]
Message-ID: <3t4Pzf6KdDz9rxw@ozlabs.org> (raw)
In-Reply-To: <20161013021714.6624-1-npiggin@gmail.com>
On Thu, 2016-13-10 at 02:17:14 UTC, Nicholas Piggin wrote:
> This patch does a couple of things. First of all, powernv immediately
> explodes when running a relocated kernel, because the system reset
> exception for handling sleeps does not do correct relocated branches.
>
> Secondly, the sleep handling code trashes the condition and cfar
> registers, which we would like to preserve for debugging purposes (for
> non-sleep case exception).
>
> This patch changes the exception to use the standard format that saves
> registers before any tests or branches are made. It adds the test for
> idle-wakeup as an "extra" to break out of the normal exception path.
> Then it branches to a relocated idle handler that calls the various
> idle handling functions.
>
> After this patch, POWER8 CPU simulator now boots powernv kernel that is
> running at non-zero.
>
> Cc: Balbir Singh <bsingharora@gmail.com>
> Cc: Shreyas B. Prabhu <shreyas@linux.vnet.ibm.com>
> Cc: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> Acked-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
> Acked-by: Balbir Singh <bsingharora@gmail.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/fb479e44a9e240a23c2d208c2ace23
cheers
next prev parent reply other threads:[~2016-10-27 11:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 2:17 [PATCH] powerpc/64s: relocation, register save fixes for system reset interrupt Nicholas Piggin
2016-10-13 11:02 ` Gautham R Shenoy
2016-10-13 11:54 ` Balbir Singh
2016-10-14 3:16 ` Nicholas Piggin
2016-10-14 5:45 ` Balbir Singh
2016-10-27 11:38 ` Michael Ellerman [this message]
2016-10-28 12:01 ` Balbir Singh
2016-11-02 6:04 ` [PATCH] " Mahesh Jagannath Salgaonkar
2016-11-02 6:57 ` Nicholas Piggin
2016-11-02 8:24 ` Mahesh J Salgaonkar
2016-11-02 8:36 ` Nicholas Piggin
2016-11-02 8:45 ` Gautham R Shenoy
2016-11-03 5:21 ` Nicholas Piggin
2016-11-03 5:56 ` Shreyas B. Prabhu
2016-11-03 6:17 ` Nicholas Piggin
2016-11-03 6:32 ` Shreyas B. Prabhu
2016-11-03 7:02 ` Nicholas Piggin
2016-11-04 9:04 ` Gautham R Shenoy
2016-11-04 11:47 ` 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=3t4Pzf6KdDz9rxw@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=ego@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=shreyas@linux.vnet.ibm.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).