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>,
David Daney <david.daney@cavium.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jan Beulich <jbeulich@suse.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung.kim@lge.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Stephane Eranian <eranian@google.com>,
arnaldo.melo@gmail.com
Subject: Re: [GIT PULL 0/9] perf/core improvements and fixes
Date: Thu, 26 Jan 2012 12:16:48 +0100 [thread overview]
Message-ID: <20120126111648.GH3853@elte.hu> (raw)
In-Reply-To: <1327446481-5505-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> This is a signed tag, please lemme know if everything went well.
>
> The --uid feature works for root, we still need to
> sort out that paranoia with some threads owned by a user that
> prevents 'perf --uid non-root-user' to work for
> 'non-root-user'.
Just wondering what detail causes that failure - the whole point
of --uid mingo would be to enable nonprivileged users to do
'session wide' profiling, *especially* if paranoia is high.
So what does --uid do which perf record --pid 1234 wouldnt
already do? By all means --uid ought to be a fancy way of doing
a whole bunch of perf record --pid 1234 profiling sessions, at
once.
[ Btw, we should probably alias --user to --uid as well, as that
might be the intuitive thing people would typically use? ]
> http://git.kernel.org/?p=linux/kernel/git/acme/linux.git;a=tag;h=ce9600c4c664ce7f97e8aa5e756b0b4ea5b017c7
> looks ok to me, need just to improve on the commit log message, I'll get
> used to it :-)
>
> - Arnaldo
>
> The following changes since commit 172d1b0b73256551f100fc00c69e356d047103f5:
>
> perf tools: Fix compile error on x86_64 Ubuntu (2012-01-08 13:34:55 -0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux perf-core-for-mingo
>
> for you to fetch changes up to f8f4b2872295dca88339ec0c403b2217b1197353:
>
> perf tools: Fix strlen() bug in perf_event__synthesize_event_type() (2012-01-24 20:31:34 -0200)
>
> ----------------------------------------------------------------
> perf/core improvements and fixes
>
> ----------------------------------------------------------------
Anyway, pulled, thanks a lot Arnaldo!
One detail: don't we want some of these fixes cherry-picked into
perf/urgent as well?
Thanks,
Ingo
next prev parent reply other threads:[~2012-01-26 11:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 23:07 Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 1/9] perf tools: Add fprintf methods for thread_map and cpu_map classes Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 2/9] perf tools: Introduce per user view Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 3/9] perf bench: Make "default" memcpy() selection actually use glibc's implementation Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 4/9] perf bench: Also allow measuring alternative memcpy implementations Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 5/9] perf bench: Also allow measuring memset() Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 6/9] perf bench: Allow passing an iteration count to "bench mem mem{cpy,set}" Arnaldo Carvalho de Melo
2012-01-24 23:07 ` [PATCH 7/9] perf tools: Fix broken build by defining _GNU_SOURCE in Makefile Arnaldo Carvalho de Melo
2012-01-24 23:08 ` [PATCH 8/9] perf probe: Usability fixes Arnaldo Carvalho de Melo
2012-01-24 23:08 ` [PATCH 9/9] perf tools: Fix strlen() bug in perf_event__synthesize_event_type() Arnaldo Carvalho de Melo
2012-01-26 11:16 ` Ingo Molnar [this message]
2012-01-26 12:22 ` Fixing perf top --user shortcoming was: Re: [GIT PULL 0/9] perf/core improvements and fixes Arnaldo Carvalho de Melo
2012-01-26 13:09 ` Ingo Molnar
2012-01-26 14:30 ` Arnaldo Carvalho de Melo
2012-01-26 18:32 ` Ingo Molnar
2012-01-26 19:24 ` Arnaldo Carvalho de Melo
2012-09-08 20:36 Arnaldo Carvalho de Melo
2012-09-09 8:40 ` Ingo Molnar
2012-10-26 14:31 Arnaldo Carvalho de Melo
2012-10-26 14:54 ` Ingo Molnar
2012-10-26 15:06 ` David Ahern
2012-10-26 15:31 ` Namhyung Kim
2012-10-26 15:34 ` Borislav Petkov
2012-10-26 16:31 ` Arnaldo Carvalho de Melo
2012-10-26 17:20 ` Borislav Petkov
2012-10-27 9:16 ` Namhyung Kim
2012-10-27 14:29 ` Arnaldo Carvalho de Melo
2012-10-27 17:12 ` stephane eranian
2012-10-26 17:05 ` Arnaldo Carvalho de Melo
2012-10-27 13:19 ` Ingo Molnar
2012-10-30 8:18 ` Ingo Molnar
2012-10-30 8:21 ` Peter Zijlstra
2012-10-30 9:14 ` Ingo Molnar
2014-05-28 13:20 Jiri Olsa
2014-06-03 20:36 Jiri Olsa
2014-06-05 8:45 ` Ingo Molnar
2014-06-19 16:38 Jiri Olsa
2015-08-10 20:56 Arnaldo Carvalho de Melo
2015-08-12 10:18 ` Ingo Molnar
2015-08-21 16:10 Arnaldo Carvalho de Melo
2015-08-22 6:47 ` Ingo Molnar
2015-09-23 1:57 Arnaldo Carvalho de Melo
2015-09-23 7:45 ` Ingo Molnar
2015-12-11 14:22 Arnaldo Carvalho de Melo
2015-12-14 8:32 ` Ingo Molnar
2017-04-01 2:10 Arnaldo Carvalho de Melo
2017-04-01 10:44 ` 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=20120126111648.GH3853@elte.hu \
--to=mingo@elte.hu \
--cc=acme@infradead.org \
--cc=arnaldo.melo@gmail.com \
--cc=david.daney@cavium.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jbeulich@suse.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.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