From: Rabin Vincent <rabin@rab.in>
To: Bradley Hanna <brahan.ml@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Creating syscalls: Under an x86_64 arch, where is the syscall table located?
Date: Sat, 5 Jul 2008 21:59:04 +0530 [thread overview]
Message-ID: <20080705162903.GA1861@debian> (raw)
In-Reply-To: <486F8D55.2060506@gmail.com>
On Sat, Jul 05, 2008 at 11:03:49AM -0400, Bradley Hanna wrote:
> I am trying to create a syscall for testing purposes. I have a kernel
> configured for x86_64 arch and need to know where the syscall table is
> located. I believe I have found the unistd.h file that I need under
> 'include/asm/unistd_64.h' but I cannot find a file containing the
> 'sys_call_table' that corresponds with that 'unistd_64.h' file. I can
> find a file called syscall_table_32.S, but no table for 64. The table
> is no longer located in entry.S, so where do I find it? The
> '__syscallN' macro is not finding my syscall definition.
sys_call_table for x86_64 is defined in arch/x86/kernel/syscall_64.c.
Rabin
prev parent reply other threads:[~2008-07-05 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 15:03 Creating syscalls: Under an x86_64 arch, where is the syscall table located? Bradley Hanna
2008-07-05 16:29 ` Rabin Vincent [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=20080705162903.GA1861@debian \
--to=rabin@rab.in \
--cc=brahan.ml@gmail.com \
--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