From: Roland McGrath <roland@redhat.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/17] arm: user_regset: iWMMXt in core dumps
Date: Mon, 27 Apr 2009 19:53:47 -0700 (PDT) [thread overview]
Message-ID: <20090428025347.63D18FC3C6@magilla.sf.frob.com> (raw)
In-Reply-To: Paul Mundt's message of Tuesday, 28 April 2009 07:43:55 +0900 <20090427224355.GD5033@linux-sh.org>
> Are these note definitions centrally defined anywhere? I looked at the
> include/elf/common.h in gdb, but it seemed fairly similar to linux/elf.h.
linux/elf.h constitutes the central place. (And basically, de facto
everyone now seems to check with me for new ones.) New user_regset types
all get the "LINUX" note name, so there is no real authority beyond the
kernel maintainers to harmonize with.
> Both sh and mips would benefit from a note type for DSP registers. Would
> something like an NT_PRDSPREG be accetable for this? Also, the note
> definitions seem to have hopped from 4 to 6, is there a definition for 5,
> or can that be used for a DSP register note type?
There is no particular benefit to packing the space. It's just a 32-bit
identifier, with existing values assigned that are both large and small.
Please do not use any more small values. They are used on other systems
that some tools already deal with, and it just keeps things simpler not to
add any new n_type values that are reused with different names on different
systems. (I'll NAK any new use of values <= 20, which already have names
in glibc's elf.h.)
For a new purpose, it is my inclination to use a new NT_<machine>_<type>
name and pick a new value range, e.g. NT_SH_* at 0x300+n. The
interpretation of these type codes is machine-specific, but it just seems
simpler to assign a new block of numbers to each machine and not have any
overlaps.
If you really mean a new particular note format that would actually match
across different machines, then a new generically-named type for that is
appropriate. For that, I'd start with another new value range like 0x10000+n
(leaving the 0x?00+n blocks to be assigned for particular arch's).
Thanks,
Roland
next prev parent reply other threads:[~2009-04-28 2:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 0:06 [PATCH 0/17] tracehook & user_regset for ARM Roland McGrath
2009-04-25 0:07 ` [PATCH 01/17] arm: arch_ptrace clean-up Roland McGrath
2009-06-19 9:13 ` Russell King
2009-06-24 6:55 ` Roland McGrath
2009-04-25 0:08 ` [PATCH 02/17] arm: arch_ptrace indentation Roland McGrath
2009-04-25 0:08 ` [PATCH 03/17] arm: tracehook_report_syscall Roland McGrath
2009-04-25 0:09 ` [PATCH 04/17] arm: tracehook_signal_handler Roland McGrath
2009-04-25 0:09 ` [PATCH 05/17] arm: TIF_NOTIFY_RESUME Roland McGrath
2009-04-25 0:10 ` [PATCH 06/17] arm: user_regset: general regs Roland McGrath
2009-04-25 0:10 ` [PATCH 07/17] arm: user_regset: FPU regs Roland McGrath
2009-04-25 0:11 ` [PATCH 08/17] arm: CORE_DUMP_USE_REGSET Roland McGrath
2009-04-25 0:11 ` [PATCH 09/17] arm: user_regset: VFP regs Roland McGrath
2009-04-25 0:12 ` [PATCH 10/17] arm: user_regset: VFP in core dumps Roland McGrath
2009-04-25 0:12 ` [PATCH 11/17] arm: user_regset: iWMMXt regs Roland McGrath
2009-04-25 0:12 ` [PATCH 12/17] arm: user_regset: iWMMXt in core dumps Roland McGrath
2009-04-27 22:43 ` Paul Mundt
2009-04-28 2:53 ` Roland McGrath [this message]
2009-04-25 0:13 ` [PATCH 13/17] arm: user_regset: Crunch regs Roland McGrath
2009-04-25 0:13 ` [PATCH 14/17] arm: user_regset: Crunch in core dumps Roland McGrath
2009-04-25 0:14 ` [PATCH 15/17] arm: user_regset: thread pointer " Roland McGrath
2009-04-25 0:15 ` [PATCH 16/17] arm: asm/syscall.h (unfinished) Roland McGrath
2009-06-19 9:31 ` Russell King
2009-06-24 8:56 ` Roland McGrath
2009-04-25 0:15 ` [PATCH 17/17] arm: HAVE_ARCH_TRACEHOOK Roland McGrath
2009-06-06 14:42 ` [PATCH 0/17] tracehook & user_regset for ARM Christoph Hellwig
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=20090428025347.63D18FC3C6@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=hch@lst.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®