LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: george anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Standard way of generating assembler offsets
Date: Fri, 05 Oct 2001 15:48:58 +1000 [thread overview]
Message-ID: <4054.1002260938@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 04 Oct 2001 08:36:54 MST." <3BBC8216.4B708192@mvista.com>
On Thu, 04 Oct 2001 08:36:54 -0700,
george anzinger <george@mvista.com> wrote:
>The symbol name IMHO should contain both the member name and the
>structure name. Otherwise there may be a problem if two structures use
>the same member name (flags comes to mind).
The asm symbol name is arch defined, I am defining the standard method,
not the asm names. It is up to the arch maintainers to pick suitable
names, e.g. ia64 does
DEFINE(IA64_SWITCH_STACK_AR_BSPSTORE_OFFSET, offsetof(struct switch_stack, ar_bspstore),);
>This is way down on the list, but is it possible to generate a separate
>file for each *.S AND put the "required symbols" in the *.S.
That works for a small number of mappings but not when there are a
large number that are required in several places. Take a look at
arch/ia64/tools/print_offsets.c, 130+ mappings used by 5 or 6 different
asm sources. There are also technical reasons (to do with the kernel
CONFIG system) why a single asm-offsets file is easier to maintain.
next prev parent reply other threads:[~2001-10-05 5:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 11:47 Keith Owens
2001-10-04 15:36 ` george anzinger
2001-10-05 5:48 ` Keith Owens [this message]
2001-10-06 5:21 ` Keith Owens
2001-10-08 9:35 ` Pantelis Antoniou
2001-10-08 17:29 ` george anzinger
2001-10-08 17:56 ` Georg Nikodym
2001-10-08 19:00 ` george anzinger
2001-10-09 7:38 ` Pantelis Antoniou
2001-10-09 9:28 ` David S. Miller
2001-10-08 9:49 ` David S. Miller
2001-10-09 7:25 ` Pantelis Antoniou
2001-10-09 9:24 ` David S. Miller
2001-10-14 11:27 ` Keith Owens
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=4054.1002260938@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [RFC] Standard way of generating assembler offsets' \
/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
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).