From: eranian@googlemail.com
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, mingo@elte.hu, x86@kernel.org,
andi@firstfloor.org, eranian@gmail.com, sfr@canb.auug.org.au
Subject: [patch 19/24] perfmon: X86 32-bit system calls support (x86)
Date: Wed, 26 Nov 2008 00:42:48 -0800 (PST) [thread overview]
Message-ID: <492d0c08.0b38560a.49b0.ffffbce9@mx.google.com> (raw)
This patchs adds the entry points for the X86 32-bit perfmon system calls.
Signed-off-by: Stephane Eranian <eranian@gmail.com>
--
Index: o3/arch/x86/kernel/syscall_table_32.S
===================================================================
--- o3.orig/arch/x86/kernel/syscall_table_32.S 2008-11-03 10:44:00.000000000 +0100
+++ o3/arch/x86/kernel/syscall_table_32.S 2008-11-03 11:18:20.000000000 +0100
@@ -332,3 +332,8 @@
.long sys_dup3 /* 330 */
.long sys_pipe2
.long sys_inotify_init1
+ .long sys_pfm_create
+ .long sys_pfm_write
+ .long sys_pfm_read /* 335 */
+ .long sys_pfm_attach
+ .long sys_pfm_set_state
Index: o3/arch/x86/include/asm/unistd_32.h
===================================================================
--- o3.orig/arch/x86/include/asm/unistd_32.h 2008-11-03 11:23:44.000000000 +0100
+++ o3/arch/x86/include/asm/unistd_32.h 2008-11-03 11:25:12.000000000 +0100
@@ -338,6 +338,11 @@
#define __NR_dup3 330
#define __NR_pipe2 331
#define __NR_inotify_init1 332
+#define __NR_pfm_create 333
+#define __NR_pfm_write (__NR_pfm_create+1)
+#define __NR_pfm_read (__NR_pfm_create+2)
+#define __NR_pfm_attach (__NR_pfm_create+3)
+#define __NR_pfm_set_state (__NR_pfm_create+4)
#ifdef __KERNEL__
--
next reply other threads:[~2008-11-26 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 8:42 eranian [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-25 21:36 [patch 19/24] perfmon: X86 32-bit system calls support (x86) eranian
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=492d0c08.0b38560a.49b0.ffffbce9@mx.google.com \
--to=eranian@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.