linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Simon Horman <horms@verge.net.au>,
	<linuxppc-dev@lists.ozlabs.org>, <kexec@lists.infradead.org>
Subject: Re: [PATCH 2/2] ppc64: Add a flag to tell the kernel it's booting from kexec
Date: Mon, 17 Aug 2015 22:30:50 -0500	[thread overview]
Message-ID: <1439868650.15601.61.camel@freescale.com> (raw)
In-Reply-To: <1439866271.1763.5.camel@ellerman.id.au>

On Tue, 2015-08-18 at 12:51 +1000, Michael Ellerman wrote:
> On Mon, 2015-08-17 at 13:59 -0500, Scott Wood wrote:
> > On Sat, 2015-07-18 at 14:57 -0500, Scott Wood wrote:
> > > It needs to know this because the SMP release mechanism for Freescale
> > > book3e is different from when booting with normal hardware.  In theory
> > > we could simulate the normal spin table mechanism, but not (easily) at
> > > the addresses U-Boot put in the device tree -- so there'd need to be
> > > even more communication between the kernel and kexec to set that up.
> > > Since there's already a similar flag being set (for kdump only), this
> > > seemed like a reasonable approach.
> > > 
> > > Signed-off-by: Scott Wood <scottwood@freescale.com>
> > > ---
> > >  kexec/arch/ppc64/kexec-elf-ppc64.c | 11 ++++++++++-
> > >  kexec/arch/ppc64/kexec-ppc64.h     |  2 ++
> > >  purgatory/arch/ppc64/v2wrap.S      | 11 +++++++++++
> > >  3 files changed, 23 insertions(+), 1 deletion(-)
> > 
> > Any comment on these two patches?
> 
> We should probably reserve 0x58 in the kernel's head_64.S too?

That's done in http://patchwork.ozlabs.org/patch/497417/

Or do you mean that you want the kernel change to go in before the userspace 
change?

-Scott

  reply	other threads:[~2015-08-18  3:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18 19:57 [PATCH 1/2] ppc64: Fix warnings Scott Wood
2015-07-18 19:57 ` [PATCH 2/2] ppc64: Add a flag to tell the kernel it's booting from kexec Scott Wood
2015-08-17 18:59   ` Scott Wood
2015-08-18  2:51     ` Michael Ellerman
2015-08-18  3:30       ` Scott Wood [this message]
2015-08-18  3:53         ` Michael Ellerman

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=1439868650.15601.61.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).