linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: James Hogan <james.hogan@imgtec.com>,
	linux-arch@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in cond_syscall
Date: Fri, 24 Feb 2012 11:19:42 -0500	[thread overview]
Message-ID: <201202241119.44480.vapier@gentoo.org> (raw)
In-Reply-To: <201202241424.07319.arnd@arndb.de>

[-- Attachment #1: Type: Text/Plain, Size: 1833 bytes --]

On Friday 24 February 2012 09:24:07 Arnd Bergmann wrote:
> On Friday 24 February 2012, James Hogan wrote:
> > Some architectures have symbol prefixes and set CONFIG_SYMBOL_PREFIX,
> > but this wasn't taken into account by the generic cond_syscall. It's
> > easy enough to fix in a generic fashion, so add the symbol prefix to
> > symbol names in cond_syscall when CONFIG_SYMBOL_PREFIX is set.
> > 
> >  include/asm-generic/unistd.h |    9 ++++++++-
> >  1 files changed, 8 insertions(+), 1 deletions(-)
> > 
> > --- a/include/asm-generic/unistd.h
> > +++ b/include/asm-generic/unistd.h
> >  
> >  #ifndef cond_syscall
> > -#define cond_syscall(x) asm(".weak\t" #x "\n\t.set\t" #x
> > ",sys_ni_syscall")
> > +#ifdef CONFIG_SYMBOL_PREFIX
> > +#define __SYMBOL_PREFIX CONFIG_SYMBOL_PREFIX
> > +#else
> > +#define __SYMBOL_PREFIX
> > +#endif
> > +#define cond_syscall(x) asm(".weak\t" __SYMBOL_PREFIX #x "\n\t" \
> > +                           ".set\t" __SYMBOL_PREFIX #x "," \
> > +                           __SYMBOL_PREFIX "sys_ni_syscall")
> > 
> >  #endif
> 
> Our trend is to move away from arch specific Kconfig symbols and
> __ARCH_HAS_* macros towards just defining whatever you need in the
> architecture as an override for the generic definition.

i don't see how __ARCH_HAS_xxx would help here.  the symbol prefix is a string, 
not a bool value.  it's also already used by linux/export.h, asm-
generic/vmlinux.lds.h, and module code in scripts/.

> Just provide your own unistd.h that does

the point of asm-generic is so that arches don't have to keep copying & 
pasting things that they really don't care about.  James' proposed patch looks 
good to me.  it might be nice to go even further and add logic to a core 
header so that CONFIG_SYMBOL_PREFIX is always defined ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-02-24 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 14:01 [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in cond_syscall James Hogan
2012-02-24 14:01 ` James Hogan
2012-02-24 14:23 ` Arnd Bergmann
2012-02-24 14:24 ` Arnd Bergmann
2012-02-24 14:24   ` Arnd Bergmann
2012-02-24 14:51   ` James Hogan
2012-02-24 15:09     ` Arnd Bergmann
2012-02-24 15:09       ` Arnd Bergmann
2012-02-24 15:40       ` James Hogan
2012-02-24 16:19   ` Mike Frysinger [this message]
2012-02-24 16:37     ` Arnd Bergmann
2012-02-24 16:38       ` Arnd Bergmann
2012-02-24 16:56         ` James Hogan
2012-02-24 16:41 ` Mike Frysinger

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=201202241119.44480.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=arnd@arndb.de \
    --cc=james.hogan@imgtec.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).