From: Michael Ellerman <mpe@ellerman.id.au>
To: Anton Blanchard <anton@samba.org>
Cc: rusty@rustcorp.com.au, Ulrich.Weigand@de.ibm.com,
paulus@samba.org, alistair@popple.id.au,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4/9] powerpc: Set eflags correctly for ELF ABIv2 core dumps.
Date: Thu, 21 Nov 2013 22:58:10 +1100 [thread overview]
Message-ID: <20131121115809.GE15913@concordia> (raw)
In-Reply-To: <1384946106-18200-5-git-send-email-anton@samba.org>
On Wed, Nov 20, 2013 at 10:15:01PM +1100, Anton Blanchard wrote:
> From: Rusty Russell <rusty@rustcorp.com.au>
>
> We leave it at zero (though it could be 1) for old tasks.
There's no issue with a v1 binary producing a v0 core dump?
I can't think of why there would be, if they are equivalent.
cheers
next prev parent reply other threads:[~2013-11-21 11:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 11:14 [PATCH 0/9] ppc64 little endian updates Anton Blanchard
2013-11-20 11:14 ` [PATCH 1/9] powerpc/pseries: Fix endian issues in pseries EEH code Anton Blanchard
2013-11-20 11:14 ` [PATCH 2/9] pseries: Add H_SET_MODE to change exception endianness Anton Blanchard
2013-11-21 11:51 ` Michael Ellerman
2013-11-20 11:15 ` [PATCH 3/9] powerpc: Add TIF_ELF2ABI flag Anton Blanchard
2013-11-21 11:55 ` Michael Ellerman
2013-12-01 10:30 ` Rusty Russell
2013-11-20 11:15 ` [PATCH 4/9] powerpc: Set eflags correctly for ELF ABIv2 core dumps Anton Blanchard
2013-11-21 11:58 ` Michael Ellerman [this message]
2013-11-20 11:15 ` [PATCH 5/9] powerpc: ELF2 binaries launched directly Anton Blanchard
2013-11-20 11:15 ` [PATCH 6/9] powerpc: ELF2 binaries signal handling Anton Blanchard
2013-11-20 11:15 ` [PATCH 7/9] powerpc: Don't use ELFv2 ABI to build the kernel Anton Blanchard
2013-11-20 11:15 ` [PATCH 8/9] powerpc: Add CONFIG_CPU_LITTLE_ENDIAN kernel config option Anton Blanchard
2013-11-21 12:05 ` Michael Ellerman
2013-11-20 11:15 ` [PATCH 9/9] powerpc: Add pseries_le_defconfig Anton Blanchard
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=20131121115809.GE15913@concordia \
--to=mpe@ellerman.id.au \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=alistair@popple.id.au \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
/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.