Could someone tell me more about the asmlinkage

From: Roy Lee
Date: Sat Jun 18 2005 - 08:59:05 EST

"Why is there a asmlinkage before a syscall?"

I know this is a FAQ already, but I couldn't find an answer that clear enough
for me to understand after "gooling" for some time. I've also read the FAQ of

The following is quoted from the FAQ of kernelnewbies.
The asmlinkage tag is one other thing that we should observe about this simple
function. This is a #define for some gcc magic that tells the compiler that the
function should not expect to find any of its arguments in registers (a common
optimization), but only on the CPU's stack. Recall our earlier assertion that
system_call consumes its first argument, the system call number, and allows up
to four more arguments that are passed along to the real system call. system_call
achieves this feat simply by leaving its other arguments (which were passed to it
in registers) on the stack. All system calls are marked with the asmlinkage tag,
so they all look to the stack for arguments. Of course, in sys_ni_syscall's case,
this doesn't make any difference, because sys_ni_syscall doesn't take any arguments,
but it's an issue for most other system calls. And, because you'll be seeing asmlinkage
in front of many other functions, I thought you should know what it was about.

It says that "To tell a compiler not to use the argument in the registers". but the
syscall's argument does pass the arguments though registers, doesn't it?

While tracing the code, I found the asmlinkage was a #define of a extern "C", and
the only usage of extern "C" that I know is to avoid the name mangling while calling
a C function in C++. Does the asmlinkage here have connection with that?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at