linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>,
	Hamish Martin <hamish.martin@alliedtelesis.co.nz>
Cc: paulus@samba.org, mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] Allow configurable stack size (especially 32k on PPC64)
Date: Wed, 22 Feb 2017 09:31:38 +1100	[thread overview]
Message-ID: <1487716298.23576.197.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170221125100.GA12237@visitor2.iram.es>

On Tue, 2017-02-21 at 13:51 +0100, Gabriel Paubert wrote:
> For now it has only been used for little-endian kernel and
> applications,
> but according to messages that I have seen on the list, switching the
> kernel 
> to Elf V2 should be possible.

I don't think the toolchain "supports" ELFv2 on BE. It sort-of seems to
work but it's not supported.

Cheers,
Ben.

  reply	other threads:[~2017-02-21 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 20:24 [PATCH 0/2] Allow configurable stack size (especially 32k on PPC64) Hamish Martin
2017-02-20 20:24 ` [PATCH 1/2] powerpc: Move THREAD_SHIFT config to KConfig Hamish Martin
2017-02-20 20:24 ` [PATCH 2/2] powerpc64: Allow for THREAD_SIZE > 16k Hamish Martin
2017-02-21 12:51 ` [PATCH 0/2] Allow configurable stack size (especially 32k on PPC64) Gabriel Paubert
2017-02-21 22:31   ` Benjamin Herrenschmidt [this message]
2017-02-22  6:25 ` Michael Ellerman
2017-02-22  8:06   ` Benjamin Herrenschmidt
2017-02-24  0:40     ` Hamish Martin
2017-02-24  0:35   ` Hamish Martin

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=1487716298.23576.197.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=hamish.martin@alliedtelesis.co.nz \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paubert@iram.es \
    --cc=paulus@samba.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).