From: Stephane Eranian <eranian@hpl.hp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 19/22] 2.6.22-rc3 perfmon2 : modified x86_64 files
Date: Thu, 31 May 2007 07:26:07 -0700 [thread overview]
Message-ID: <20070531142607.GI22798@frankl.hpl.hp.com> (raw)
In-Reply-To: <20070531142038.GB2538@one.firstfloor.org>
Andi,
On Thu, May 31, 2007 at 04:20:38PM +0200, Andi Kleen wrote:
>
> > > Just use a cpu notifier instead. No need to add everybody's per cpu init code here.
> >
> > The code must run on the CPU that is being initialized.
>
> smp_call_function_single()
>
Isn't that more complicated than just adding a hook in cpu_disable()?
> > >
> > > No compat syscalls?
> > >
> > compat syscalls for what? I need to ensure backward compatiblity on IA-64 only.
>
> For 32bit / i386 code.
I's there in ia32entry.S. Was it missing from the E-mail?
In anycase, here it is:
diff --exclude=.git -urp linux-2.6.22.base/arch/x86_64/ia32/ia32entry.S linux-2.6.22/arch/x86_64/ia32/ia32entry.S
--- linux-2.6.22.base/arch/x86_64/ia32/ia32entry.S 2007-05-29 03:17:16.000000000 -0700
+++ linux-2.6.22/arch/x86_64/ia32/ia32entry.S 2007-05-29 03:24:14.000000000 -0700
@@ -719,4 +719,16 @@ ia32_sys_call_table:
.quad compat_sys_signalfd
.quad compat_sys_timerfd
.quad sys_eventfd
+ .quad sys_pfm_create_context
+ .quad sys_pfm_write_pmcs
+ .quad sys_pfm_write_pmds
+ .quad sys_pfm_read_pmds
+ .quad sys_pfm_load_context
+ .quad sys_pfm_start
+ .quad sys_pfm_stop
+ .quad sys_pfm_restart
+ .quad sys_pfm_create_evtsets
+ .quad sys_pfm_getinfo_evtsets
+ .quad sys_pfm_delete_evtsets
+ .quad sys_pfm_unload_context
ia32_syscall_end:
--
-Stephane
prev parent reply other threads:[~2007-05-31 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 13:48 Stephane Eranian
2007-05-31 15:05 ` Andi Kleen
2007-05-31 14:16 ` Stephane Eranian
2007-05-31 14:20 ` Andi Kleen
2007-05-31 14:26 ` Stephane Eranian [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=20070531142607.GI22798@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=andi@firstfloor.org \
--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
all inboxes | Powered by JetHome®