kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] kexec/ppc64: bring up new ppc64le architecture
Date: Wed, 20 Nov 2013 11:48:58 +0100	[thread overview]
Message-ID: <528C939A.80507@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131119010140.GA17628@verge.net.au>

On 19/11/2013 02:01, Simon Horman wrote:
> On Fri, Nov 15, 2013 at 04:01:51PM +0100, Laurent Dufour wrote:
>> This patch provides support for the new Power PC litte endian (LE) mode. The
>> LE mode only differs in the way the instructions and data are stored in memory
>> thus there is no real need to duplicate the ppc64 code.
>>
>> However some compilation's options, especially for the purgatory, differ
>> between little and big endian mode's support. A new "SUBARCH" build variable
>> is introduced which is currently only used for PPC64 to specify the
>> endianness.
>>
>> Another set of changes in this patch is fixing minor endianess issues in the
>> ppc64 code and fix an alignment issue raised on Power7 little endian mode.
>> Among these fixes, the check on the kernel binary endianess is removed,
>> since we can imagine kexecing a LE kernel from a BE environment, as far as
>> the specified root filesystem and initrd file are containing the right
>> binaries.
>>
>> This patch depends on the patch "kexec/ppc64: use common architecture
>> fs2dt.c file" I sent earlier on the kexec mailing list.
>>
>> Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
> 
> Hi Laurent,
> 
> I have applied this. But could you let me know how to (cross) compile it?

Hi Simon,

Thanks for applying the patches.

I didn't use the cross the compilation mechanism. I tried to make it run
but I faced some issues and looking at the Makefile, especially the
kexec/Makefile file it doesn't look to be designed to do cross
compilation since there is no reference to TARGET_CC. May be I didn't
use it in the right way. If you have any tips on that...

I did my builds and tests using a qemu guest and KVM running ppc64 LE
binaries since currently there is no other way to run a Power in little
endian mode.

Unfortunately, such a root file system image is not currently available
outside of IBM and the Open Power's partners. Despite must of the patch
have been pushed to the community, I'm sorry to not being allowed to
provide you with a root file system image with LE binaries. Be sure I'd
do otherwise.

Theoretically all the parts needed to build a PPC64 LE rootfs are
available, binutils/gcc/glibc/buildroot, but that's a lot of effort.

Please note that the PPC64 LE support is still a moving target, and an
ABI change is about to be released which would imply a massive rebuild.
I hope once this will be done this will be easier to get LE root file
system outside of IBM.

Cheers,
Laurent.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2013-11-20 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 15:01 [PATCH] kexec/ppc64: bring up new ppc64le architecture Laurent Dufour
2013-11-19  1:01 ` Simon Horman
2013-11-20 10:48   ` Laurent Dufour [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=528C939A.80507@linux.vnet.ibm.com \
    --to=ldufour@linux.vnet.ibm.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.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 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).