From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: asmlinkage
Date: Wed, 12 May 2010 21:13:56 +0100 [thread overview]
Message-ID: <20100512201356.GA5611@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTimYY_ljcTwRTQSaVBtUGZE_3dWX1PUbNFPXzTnR@mail.gmail.com>
On Mon, May 10, 2010 at 12:49:24AM +0300, Alexander (Sasha) Sirotkin wrote:
> Sorry for yet another basic question, but why "asmlinkage" is an empty macro
> on ARM?
ARM doesn't require any special API modification to call functions
from assembly.
x86 has two different calling conventions - one is to stack all function
arguments, the other passes some arguments via registers. asmlinkage
selects between them.
However, we keep the asmlinkage labelling on ARM because it's useful to
indicate which functions are called by assembly - and therefore which
need closer inspection when their signature is changed to make sure the
assembly calling them is also fixed.
prev parent reply other threads:[~2010-05-12 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 21:49 asmlinkage Alexander (Sasha) Sirotkin
2010-05-12 20:13 ` Russell King - ARM Linux [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=20100512201356.GA5611@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;
as well as URLs for NNTP newsgroup(s).