From: Simon Horman <horms@verge.net.au>
To: Scott Wood <scottwood@freescale.com>
Cc: kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH v2 3/3] ppc64: Add a flag to tell the kernel it's booting from kexec
Date: Fri, 16 Oct 2015 10:48:38 +0900 [thread overview]
Message-ID: <20151016014838.GG20667@verge.net.au> (raw)
In-Reply-To: <1444172150-29493-3-git-send-email-scottwood@freescale.com>
On Tue, Oct 06, 2015 at 05:55:50PM -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.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> v2: Use a device tree property rather than setting a flag in the kernel
> image, as requested by Michael Ellerman.
I'd value a review of this from someone more familiar with ppc than I.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-10-16 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 22:55 [PATCH v2 1/3] ppc64: Fix warnings Scott Wood
2015-10-06 22:55 ` [PATCH v2 2/3] ppc64: Avoid rfid if no need to clear MSR_LE Scott Wood
2015-10-16 1:48 ` Simon Horman
2015-10-30 0:16 ` Scott Wood
2015-11-01 22:55 ` Sam Mendoza-Jonas
2015-11-02 0:21 ` Sam Mendoza-Jonas
2015-11-02 2:06 ` Simon Horman
2015-10-06 22:55 ` [PATCH v2 3/3] ppc64: Add a flag to tell the kernel it's booting from kexec Scott Wood
2015-10-16 1:48 ` Simon Horman [this message]
2015-12-07 20:42 ` Scott Wood
2015-12-08 3:46 ` Michael Ellerman
2015-12-08 6:01 ` Simon Horman
2015-10-16 1:47 ` [PATCH v2 1/3] ppc64: Fix warnings Simon Horman
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=20151016014838.GG20667@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=scottwood@freescale.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