From: Tobias Klauser <tklauser@distanz.ch>
To: Chung-Lin Tang <chunglin.tang@gmail.com>
Cc: Chung-Lin Tang <cltang@codesourcery.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Arnd Bergmann <arnd@arndb.de>, Ley Foon Tan <lftan@altera.com>,
Walter Goossens <waltergoossens@home.nl>,
linux-arch@vger.kernel.org,
"nios2-dev@lists.rocketboards.org"
<nios2-dev@lists.rocketboards.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nios2: is the ptrace ABI correct?
Date: Thu, 12 Mar 2015 12:07:22 +0100 [thread overview]
Message-ID: <20150312110722.GB894@distanz.ch> (raw)
In-Reply-To: <54FDD219.1060707@gmail.com>
On 2015-03-09 at 18:02:17 +0100, Chung-Lin Tang <chunglin.tang@gmail.com> wrote:
> On 2015/3/10 12:54 AM, Chung-Lin Tang wrote:
> > It appears that some of the ways nios2 has organized the
> > ucontext/pt_regs/etc. are remnants of the pre-generic code, some
> > basically because the port was based off m68k.
> >
> > I've re-organized the headers a bit: nios2/include/asm/ucontext.h is
> > deleted, and re-definition of struct sigcontext now allows use of
> > uapi/asm-generic/ucontext.h directly. Note that the reorg, despite
> > effectively renaming some fields, is still binary compatible. I'll
> > probably update the corresponding glibc definitions later.
> >
> > struct pt_regs is now not exported, and all exported register sets are
> > now supposed to follow the 49 register set defined as in GDB now.
> >
> > Tobias, Ley Foon, how do you think this looks?
>
> Sorry, accidentally attached unrelated GCC patch instead, this one's the
> correct one.
Sorry for jumping into the discussion so late. The patch looks fine to
me as well. Only one minor nit below. Since Ley Foon already applied it
as is, I'll just send a followup patch.
Thanks Ezequiel, Chung-Lin and Ley Foon for pushing this! Looking
forward to have strace support on nios2.
[...]
> diff --git a/arch/nios2/include/uapi/asm/Kbuild b/arch/nios2/include/uapi/asm/Kbuild
> index 4f07ca3f8..37613119 100644
> --- a/arch/nios2/include/uapi/asm/Kbuild
> +++ b/arch/nios2/include/uapi/asm/Kbuild
> @@ -2,3 +2,5 @@ include include/uapi/asm-generic/Kbuild.asm
>
> header-y += elf.h
> header-y += ucontext.h
This should no longer be needed now that the non-generic ucontext.h is
gone.
next prev parent reply other threads:[~2015-03-12 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 3:04 Ezequiel Garcia
2015-02-24 8:54 ` Arnd Bergmann
2015-02-24 15:28 ` Ezequiel Garcia
2015-02-24 19:25 ` Arnd Bergmann
2015-02-25 11:33 ` Ezequiel Garcia
2015-02-25 14:07 ` Arnd Bergmann
2015-02-27 8:57 ` Chung-Lin Tang
2015-02-27 11:19 ` Ezequiel Garcia
2015-03-04 20:56 ` Ezequiel Garcia
2015-03-09 16:54 ` Chung-Lin Tang
2015-03-09 17:02 ` Chung-Lin Tang
2015-03-09 17:05 ` Ezequiel Garcia
2015-03-10 2:54 ` Ley Foon Tan
2015-03-10 6:17 ` Chung-Lin Tang
2015-03-11 7:48 ` Ley Foon Tan
2015-03-11 14:31 ` Ezequiel Garcia
2015-03-12 11:07 ` Tobias Klauser [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-24 2:30 Ezequiel Garcia
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=20150312110722.GB894@distanz.ch \
--to=tklauser@distanz.ch \
--cc=arnd@arndb.de \
--cc=chunglin.tang@gmail.com \
--cc=cltang@codesourcery.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@lists.rocketboards.org \
--cc=waltergoossens@home.nl \
/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
all inboxes | Powered by JetHome®