From: Scott Wood <scottwood@freescale.com>
To: Simon Horman <horms@verge.net.au>
Cc: 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 13:59:47 -0500 [thread overview]
Message-ID: <1439837987.15601.29.camel@freescale.com> (raw)
In-Reply-To: <1437249439-31496-2-git-send-email-scottwood@freescale.com>
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?
-Scott
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Simon Horman <horms@verge.net.au>
Cc: <kexec@lists.infradead.org>, <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] ppc64: Add a flag to tell the kernel it's booting from kexec
Date: Mon, 17 Aug 2015 13:59:47 -0500 [thread overview]
Message-ID: <1439837987.15601.29.camel@freescale.com> (raw)
In-Reply-To: <1437249439-31496-2-git-send-email-scottwood@freescale.com>
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?
-Scott
next prev parent reply other threads:[~2015-08-17 19:00 UTC|newest]
Thread overview: 12+ 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 ` 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-07-18 19:57 ` Scott Wood
2015-08-17 18:59 ` Scott Wood [this message]
2015-08-17 18:59 ` Scott Wood
2015-08-18 2:51 ` Michael Ellerman
2015-08-18 2:51 ` Michael Ellerman
2015-08-18 3:30 ` Scott Wood
2015-08-18 3:30 ` Scott Wood
2015-08-18 3:53 ` Michael Ellerman
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=1439837987.15601.29.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.