From: David Ahern <dsahern@gmail.com>
To: Jovi Zhang <bookjovi@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf: add /proc/perf_events file for dump perf events info
Date: Thu, 13 Sep 2012 15:03:45 -0600 [thread overview]
Message-ID: <50524A31.1080403@gmail.com> (raw)
In-Reply-To: <CACV3sbLJpv2KSSkrRRDVuJ6xtJOSwCKaJfhO1wMF6DgAU9eCBw@mail.gmail.com>
On 7/5/12 7:02 AM, Jovi Zhang wrote:
> From 91fbcca37a2c9979083f4b9a6fa9c1875fc2886f Mon Sep 17 00:00:00 2001
> From: Jovi Zhang <bookjovi@gmail.com>
> Date: Fri, 6 Jul 2012 00:05:40 +0800
> Subject: [PATCH] perf: add /proc/perf_events file for dump perf events info
>
> This new /proc/perf_events file is used for real time dump all
> perf events info in whole system wide machine, this patch also add
> a new field perf_entry in struct perf_event, for connect to
> global list perf_events_list.
Applied your patch to see if sheds light on a problem. Saw this
compiling the kernel:
kernel/events/proc_perf_events.c: In function ‘perf_events_proc_show’:
kernel/events/proc_perf_events.c:175:5: warning: format ‘%llu’ expects
argument of type ‘long long unsigned int’, but argument 3 has type ‘long
int’ [-Wformat]
David
prev parent reply other threads:[~2012-09-13 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 8:23 [PATCH] perf: add /proc/perf_events file for dump perf events info Jovi Zhang
2012-07-05 8:27 ` Peter Zijlstra
[not found] ` <CACV3sb+aadXJYu7_JUedCodgQmF8d1q7OxSVoz=vwfc+Ow_caA@mail.gmail.com>
2012-07-05 13:02 ` Jovi Zhang
2012-07-05 13:08 ` Peter Zijlstra
2012-07-05 13:38 ` Jovi Zhang
2012-07-05 13:54 ` Peter Zijlstra
2012-07-06 2:26 ` Jovi Zhang
2012-09-13 21:03 ` David Ahern [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=50524A31.1080403@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=bookjovi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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