public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: John Reiser <jreiser@BitWagon.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Hirokazu Takata <takata@linux-m32r.org>,
	"David S. Miller" <davem@davemloft.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	Greg Ungerer <gerg@uclinux.org>,
	Mikael Starvik <starvik@axis.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: STT_FUNC for assembler checksum and semaphore ops
Date: Tue, 8 Jan 2008 10:35:58 +0100	[thread overview]
Message-ID: <20080108093558.GG27671@elte.hu> (raw)
In-Reply-To: <47826019.9040607@BitWagon.com>


* John Reiser <jreiser@BitWagon.com> wrote:

> Dear $ARCH Maintainers,
> 
> This patch adds Elf32_Sym .st_info (STT_FUNC) and .st_size for 
> hand-coded checksum and semaphore subroutines.  I needed this info 
> when writing a static analyzer for stack depth [grovel over ./vmlinux] 
> on the um (UserModeLinux) $ARCH for i386.  The changes work on i386.  
> Other $ARCH are analogous but not tested.  Other arch/x86/lib/*.S are 
> not used by um currently.  [Should analogous changes be made anyway?]
> 
> Comments?

thanks, i have picked up the x86 bits.

Will pick up later cleanup versions as well if there's some better macro 
approach to do this as an ENTRY thing, as we could consolidate both the 
start and the end into a single macro:

        .type __down_failed_trylock, @function
ENTRY(__down_failed_trylock)
        CFI_STARTPROC

        CFI_ENDPROC
        END(__down_failed_trylock)
        .size __down_failed_trylock, . - __down_failed_trylock

perhaps START_FUNCTION() and END_FUNCTION() macros?

	Ingo

      parent reply	other threads:[~2008-01-08  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 17:23 STT_FUNC for assembler checksum and semaphore ops John Reiser
2008-01-07 19:22 ` Sam Ravnborg
2008-01-08  9:35 ` Ingo Molnar [this message]

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=20080108093558.GG27671@elte.hu \
    --to=mingo@elte.hu \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=hpa@zytor.com \
    --cc=jreiser@BitWagon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=starvik@axis.com \
    --cc=takata@linux-m32r.org \
    --cc=tglx@linutronix.de \
    --cc=zippel@linux-m68k.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