From: Simon Horman <horms@verge.net.au>
To: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Cc: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH v2] kexec/ppc64 fix device tree endianess issues for memory attributes
Date: Fri, 31 Jan 2014 14:21:24 +0900 [thread overview]
Message-ID: <20140131052124.GA25099@verge.net.au> (raw)
In-Reply-To: <20140130150622.11156.39497.stgit@nimbus>
On Thu, Jan 30, 2014 at 04:06:22PM +0100, Laurent Dufour wrote:
> All the attributes exposed in the device tree are in Big Endian format.
>
> This patch add the byte swap operation for some entries which were not yet
> processed, including those fixed by the following kernel's patch :
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-January/114720.html
>
> To work on PPC64 Little Endian mode, kexec now requires that the kernel's
> patch mentioned above is applied on the kexecing kernel.
>
> Tested on ppc64 LPAR (kexec/dump) and ppc64le in a Qemu/KVM guest (kexec)
>
> Changes from v1 :
> * add processing of the following entries :
> - ibm,dynamic-reconfiguration-memory
> - chosen/linux,kernel-end
> - chosen/linux,crashkernel-base & size
> - chosen/linux,memory-limit
> - chosen/linux,htab-base & size
> - linux,tce-base & size
> - memory@/reg
> Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Thanks, applied.
prev parent reply other threads:[~2014-01-31 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 15:06 [PATCH v2] kexec/ppc64 fix device tree endianess issues for memory attributes Laurent Dufour
2014-01-31 5:21 ` Simon Horman [this message]
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=20140131052124.GA25099@verge.net.au \
--to=horms@verge.net.au \
--cc=anton@samba.org \
--cc=kexec@lists.infradead.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).