From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 4/4] powerpc/boot: don't clobber r6 and r7 in epapr boot
Date: Wed, 11 Feb 2015 15:50:20 +1100 [thread overview]
Message-ID: <1423630220.5965.2.camel@kernel.crashing.org> (raw)
In-Reply-To: <54DADA1B.4060009@ozlabs.org>
On Wed, 2015-02-11 at 12:27 +0800, Jeremy Kerr wrote:
> Hi Ben,
>
> > You might want to also remove the use of r8 and r9 which are supposed
> > to contain the OPAL entry and base for debugging purposes. We would also
> > have to restore them before booting the kernel.
>
> I'd prefer that to be a separate change, if that's okay - it'd require
> us to change the kentry prototype, and would percolate to epapr_platform
> init too.
Ok.
Ben.
next prev parent reply other threads:[~2015-02-11 4:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 12:15 [PATCH 1/4] powerpc/boot/fdt: Add little-endian support to libfdt wrappers Jeremy Kerr
2015-02-10 12:15 ` [PATCH 2/4] powerpc/boot/wrapper: use the pseries wrapper for zImage.epapr Jeremy Kerr
2015-02-11 2:12 ` Benjamin Herrenschmidt
2015-02-11 2:16 ` Jeremy Kerr
2015-02-11 2:20 ` Benjamin Herrenschmidt
2015-02-10 12:15 ` [PATCH 3/4] powerpc/boot: Fix stack corruption in epapr entry point Jeremy Kerr
2015-02-11 2:11 ` Benjamin Herrenschmidt
2015-02-10 12:15 ` [PATCH 4/4] powerpc/boot: don't clobber r6 and r7 in epapr boot Jeremy Kerr
2015-02-11 2:09 ` Benjamin Herrenschmidt
2015-02-11 4:27 ` Jeremy Kerr
2015-02-11 4:50 ` Benjamin Herrenschmidt [this message]
2015-02-11 2:11 ` [PATCH 1/4] powerpc/boot/fdt: Add little-endian support to libfdt wrappers Benjamin Herrenschmidt
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=1423630220.5965.2.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=jk@ozlabs.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).