From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <tzanussi@gmail.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [GIT PULL 0/5] perf/urgent fixes
Date: Sat, 28 May 2011 11:41:50 +0200 [thread overview]
Message-ID: <20110528094150.GA12059@elte.hu> (raw)
In-Reply-To: <1306532736-3790-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> Please consider pulling from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/urgent
>
> Regards,
>
> - Arnaldo
>
> Arnaldo Carvalho de Melo (4):
> perf tools: Make sure kptr_restrict warnings fit 80 col terms
> perf top: Remove unused macro
> perf top: Handle kptr_restrict
> perf top: Don't stop if no kernel symtab is found
>
> David Ahern (1):
> perf events: initialize fd array to -1 instead of 0
>
> tools/perf/builtin-record.c | 19 ++++++++-----------
> tools/perf/builtin-report.c | 17 +++++++----------
> tools/perf/builtin-top.c | 37 ++++++++++++++++++++++++++++++-------
> tools/perf/util/evsel.c | 10 ++++++++++
> 4 files changed, 55 insertions(+), 28 deletions(-)
Pulled, thanks a lot Arnaldo!
The various variations of kptr_restrict now work fine AFAICS - will
send the fixes to Linus today.
One (very) small issue i noticed, if the user only samples user-space
events then i still get the warning:
aldebaran:~> perf record -e cycles:upp sleep 1
WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted,
although perf does not record any kernel samples so kptr_restrict is
irrelevant in this case.
Ingo
next prev parent reply other threads:[~2011-05-28 9:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 21:45 Arnaldo Carvalho de Melo
2011-05-27 21:45 ` [PATCH 1/5] perf tools: Make sure kptr_restrict warnings fit 80 col terms Arnaldo Carvalho de Melo
2011-05-27 21:45 ` [PATCH 2/5] perf events: initialize fd array to -1 instead of 0 Arnaldo Carvalho de Melo
2011-05-27 21:45 ` [PATCH 3/5] perf top: Remove unused macro Arnaldo Carvalho de Melo
2011-05-27 21:45 ` [PATCH 4/5] perf top: Handle kptr_restrict Arnaldo Carvalho de Melo
2011-05-27 21:45 ` [PATCH 5/5] perf top: Don't stop if no kernel symtab is found Arnaldo Carvalho de Melo
2011-05-28 9:41 ` Ingo Molnar [this message]
2011-05-29 14:12 ` [GIT PULL 0/5] perf/urgent fixes Arnaldo Carvalho de Melo
2011-05-29 14:30 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2018-10-05 16:10 Arnaldo Carvalho de Melo
2018-10-05 16:14 ` Ingo Molnar
2018-07-30 20:50 Arnaldo Carvalho de Melo
2018-07-31 5:51 ` Ingo Molnar
2018-05-14 12:23 Arnaldo Carvalho de Melo
2018-05-15 6:21 ` Ingo Molnar
2017-12-18 14:39 Arnaldo Carvalho de Melo
2017-12-18 17:11 ` Ingo Molnar
2015-12-07 20:06 Arnaldo Carvalho de Melo
2015-12-08 5:09 ` Ingo Molnar
2015-11-13 20:57 Arnaldo Carvalho de Melo
2015-11-18 5:57 ` Ingo Molnar
2015-11-11 21:56 Arnaldo Carvalho de Melo
2015-11-12 6:38 ` Ingo Molnar
2015-09-17 18:54 Arnaldo Carvalho de Melo
2015-09-18 5:46 ` Ingo Molnar
2014-02-13 21:15 Arnaldo Carvalho de Melo
2014-02-22 16:23 ` Ingo Molnar
2013-11-19 20:41 Arnaldo Carvalho de Melo
2013-11-20 13:32 ` Ingo Molnar
2013-09-10 18:11 Arnaldo Carvalho de Melo
2013-09-11 5:46 ` Ingo Molnar
2013-09-11 5:55 ` Ingo Molnar
2013-09-11 14:08 ` Arnaldo Carvalho de Melo
2013-09-12 5:45 ` Ingo Molnar
2013-12-02 6:58 ` Brian Gitonga Marete
2012-04-14 17:03 Arnaldo Carvalho de Melo
2012-04-15 6:04 ` Ingo Molnar
2012-04-05 23:28 Arnaldo Carvalho de Melo
2011-04-06 11:00 Arnaldo Carvalho de Melo
2011-04-06 11:10 ` Ingo Molnar
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=20110528094150.GA12059@elte.hu \
--to=mingo@elte.hu \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tzanussi@gmail.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
Powered by JetHome