From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Use definition for cmpxchg swi
Date: Mon, 9 Nov 2009 17:30:40 +0000 [thread overview]
Message-ID: <20091109173040.GA24358@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0911090953010.16711@xanadu.home>
On Mon, Nov 09, 2009 at 09:56:26AM -0500, Nicolas Pitre wrote:
> On Mon, 9 Nov 2009, Russell King - ARM Linux wrote:
>
> > On Sun, Nov 08, 2009 at 08:42:51PM -0500, Nicolas Pitre wrote:
> > > On Sun, 8 Nov 2009, Russell King - ARM Linux wrote:
> > >
> > > > Use a definition for the cmpxchg SWI instead of hard-coding the number.
> > >
> > > Well... Initially I didn't use a definition in unistd.h because I
> > > didn't want user space to "see" it and assume this was part of the
> > > kernel ABI since this is actually just an implementation detail that
> > > depends on a particular kernel configuration.
> >
> > The ifdef __KERNEL__ is sufficient for that - kernel headers are now
> > stripped of code within these defines during 'make installheaders'.
>
> Sure. But I wouldn't be surprised to see people redefining it manually
> just because they didn't understand why there was a #ifdef __KERNEL__ in
> the kernel file. Adding a comment makes the intent clearer.
One solution to that would be to make it a random number within a
certain range picked at kernel boot time. ;)
I'll add a comment then.
Note, however, that the original code was buggy - it resulted in
the '0xfff0' syscall being called instead of '0xffff0' - note the
extra 4 bits there.
next prev parent reply other threads:[~2009-11-09 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 20:04 [PATCH] Use definition for cmpxchg swi Russell King - ARM Linux
2009-11-09 1:42 ` Nicolas Pitre
2009-11-09 8:51 ` Russell King - ARM Linux
2009-11-09 14:56 ` Nicolas Pitre
2009-11-09 17:30 ` Russell King - ARM Linux [this message]
2009-11-09 19:08 ` Jamie Lokier
2009-11-09 19:14 ` Russell King - ARM Linux
2009-11-09 19:31 ` Nicolas Pitre
2009-11-09 23:52 ` Russell King - ARM Linux
2009-11-09 23:58 ` Nicolas Pitre
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=20091109173040.GA24358@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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