From: Peter Zijlstra <peterz@infradead.org>
To: mingo@redhat.com, hpa@zytor.com, acme@redhat.com,
linux-kernel@vger.kernel.org, will.deacon@arm.com,
matthltc@us.ibm.com, mahesh@linux.vnet.ibm.com,
rostedt@goodmis.org, tglx@linutronix.de,
prasad@linux.vnet.ibm.com, greenrd@greenrd.org, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf events: Clean up pid passing
Date: Wed, 22 Sep 2010 14:22:22 +0200 [thread overview]
Message-ID: <1285158142.2275.898.camel@laptop> (raw)
In-Reply-To: <tip-38a81da2205f94e8a2a834b51a6b99c91fc7c2e8@git.kernel.org>
On Wed, 2010-09-15 at 10:03 +0000, tip-bot for Matt Helsley wrote:
> +++ b/kernel/hw_breakpoint.c
> @@ -433,8 +433,7 @@ register_user_hw_breakpoint(struct perf_event_attr *attr,
> perf_overflow_handler_t triggered,
> struct task_struct *tsk)
> {
> - return perf_event_create_kernel_counter(attr, -1, task_pid_vnr(tsk),
> - triggered);
> + return perf_event_create_kernel_counter(attr, -1, tsk, triggered);
> }
> EXPORT_SYMBOL_GPL(register_user_hw_breakpoint);
>
That seems to have gotten lost somehow..
/usr/src/linux-2.6/kernel/hw_breakpoint.c: In function ‘register_user_hw_breakpoint’:
/usr/src/linux-2.6/kernel/hw_breakpoint.c:436: warning: passing argument 3 of ‘perf_event_create_kernel_counter’ makes pointer from integer without a cast
/usr/src/linux-2.6/include/linux/perf_event.h:909: note: expected ‘struct task_struct *’ but argument is of type ‘pid_t’
The below cures it
---
diff --git a/kernel/hw_breakpoint.c b/kernel/hw_breakpoint.c
index 8f36c99..3b714e8 100644
--- a/kernel/hw_breakpoint.c
+++ b/kernel/hw_breakpoint.c
@@ -433,7 +433,7 @@ register_user_hw_breakpoint(struct perf_event_attr *attr,
perf_overflow_handler_t triggered,
struct task_struct *tsk)
{
- return perf_event_create_kernel_counter(attr, -1, task_pid_vnr(tsk), triggered);
+ return perf_event_create_kernel_counter(attr, -1, tsk, triggered);
}
EXPORT_SYMBOL_GPL(register_user_hw_breakpoint);
next prev parent reply other threads:[~2010-09-22 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1284408080-2135-1-git-send-email-matthltc@us.ibm.com>
2010-09-13 20:01 ` [PATCH 1/3] hw breakpoints: Fix pid namespace bug Matt Helsley
2010-09-13 20:01 ` [PATCH 2/3] perf events: Split out task search into helper Matt Helsley
2010-09-15 10:03 ` [tip:perf/core] " tip-bot for Matt Helsley
2010-09-13 20:01 ` [PATCH 3/3] perf events: Cleanup pid passing Matt Helsley
2010-09-15 8:18 ` Peter Zijlstra
2010-09-15 10:03 ` [tip:perf/core] perf events: Clean up " tip-bot for Matt Helsley
2010-09-22 12:22 ` Peter Zijlstra [this message]
2010-09-15 10:03 ` [tip:perf/core] hw breakpoints: Fix pid namespace bug tip-bot for Matt Helsley
2010-09-15 11:41 ` Frederic Weisbecker
2010-09-15 11:45 ` Ingo Molnar
2010-09-17 8:28 ` [tip:perf/urgent] " tip-bot for Matt Helsley
2010-09-13 20:08 ` [PATCH 0/3] perf_events and hw_breakpoints fix and cleanup Frederic Weisbecker
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=1285158142.2275.898.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=greenrd@greenrd.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=matthltc@us.ibm.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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