From: Scott Wood <scottwood@freescale•com>
To: Tiejun Chen <tiejun.chen@windriver•com>
Cc: linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org
Subject: Re: [v3][PATCH 6/8] book3e/kexec/kdump: implement ppc64 kexec specfic
Date: Tue, 17 Dec 2013 21:45:59 -0600 [thread overview]
Message-ID: <1387338359.3140.40.camel@snotra.buserror.net> (raw)
In-Reply-To: <1373357007-30785-7-git-send-email-tiejun.chen@windriver.com>
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> ppc64 kexec mechanism has a different implementation with ppc32.
>
> Signed-off-by: Tiejun Chen <tiejun.chen@windriver•com>
Could you describe the relevant differences?
-Scott
next prev parent reply other threads:[~2013-12-18 3:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 8:03 [v3][PATCH 0/8] powerpc/book3e: support kexec and kdump Tiejun Chen
2013-07-09 8:03 ` [v3][PATCH 1/8] powerpc/book3e: rename interrupt_end_book3e with __end_interrupts Tiejun Chen
2013-07-10 5:17 ` Bhushan Bharat-R65777
2013-07-10 5:39 ` tiejun.chen
2013-12-18 3:03 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 2/8] powerpc/book3e: support CONFIG_RELOCATABLE Tiejun Chen
2013-12-18 3:29 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 3/8] book3e/kexec/kdump: enable kexec for kernel Tiejun Chen
2013-12-18 3:35 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 4/8] book3e/kexec/kdump: create a 1:1 TLB mapping Tiejun Chen
2013-12-18 3:39 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 5/8] book3e/kexec/kdump: introduce a kexec kernel flag Tiejun Chen
2013-12-18 3:42 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 6/8] book3e/kexec/kdump: implement ppc64 kexec specfic Tiejun Chen
2013-12-18 3:45 ` Scott Wood [this message]
2013-07-09 8:03 ` [v3][PATCH 7/8] book3e/kexec/kdump: redefine VIRT_PHYS_OFFSET Tiejun Chen
2013-07-10 5:20 ` Bhushan Bharat-R65777
2013-07-10 5:46 ` tiejun.chen
2013-12-18 3:48 ` Scott Wood
2013-07-09 8:03 ` [v3][PATCH 8/8] book3e/kexec/kdump: recover "r4 = 0" to create the initial TLB Tiejun Chen
2013-12-18 3:50 ` Scott Wood
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=1387338359.3140.40.camel@snotra.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=tiejun.chen@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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