From: Ingo Molnar <mingo@kernel.org> To: Michael Ellerman <mpe@ellerman.id.au> Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>, mingo@redhat.com, ak@linux.intel.com, Jiri Olsa <jolsa@redhat.com>, Arnaldo Carvalho de Melo <acme@kernel.org>, peterz@infradead.org, namhyung@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Pekka Enberg <penberg@iki.fi>, Arnaldo Carvalho de Melo <acme@infradead.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>, Thomas Gleixner <tglx@linutronix.de>, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.) Date: Tue, 14 Apr 2015 14:58:22 +0200 [thread overview] Message-ID: <20150414125822.GA32761@gmail.com> (raw) In-Reply-To: <1429010508.27414.1.camel@ellerman.id.au> * Michael Ellerman <mpe@ellerman.id.au> wrote: > On Tue, 2015-04-14 at 10:55 +0200, Ingo Molnar wrote: > > * Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> wrote: > > > > > This is another attempt to resurrect Andi Kleen's patchset so users > > > can specify perf events by their event names rather than raw codes. > > > > > > This is a rebase of Andi Kleen's patchset from Jul 30, 2014[1] to 4.0. > > > (I fixed minor and not so minor conflicts). > > > > So this series shows some progress, but instead of this limited > > checkout ability I'd still prefer it if 'perf download' downloaded > > the latest perf code itself and built it - it shouldn't be limited > > to just a small subset of the perf source code! > > Ingo, can you please stop blocking this? It's getting ridiculous. > > We've been waiting over 8 months for this to go in. We just merged a patch series that was first sent in 2013. Some things take time to get right. > While we've been waiting most of our users have learnt to use operf > instead, which doesn't require raw codes. > > I would also add that exactly zero users have asked for a feature > where perf downloads and rebuilds itself. In fact many of them would > consider that a security breach. Fetching tracing scripts, plugins or other instrumentation scripts can be considered a 'security breach' as well. Fetching external tables (or network access to begin with) can be considered a 'security breach' as well, depending on how restricted an environment is. But we don't design our code based on the most restrictive environments that are hostile to open source concepts! Unfortunate users that are not allowed to update open source code that they are using should probably not update it. The other 99.9% of perf users would benefit from a properly done upgrading/updating feature. Please stop thinking in terms of restricted, closed environments. Packaged perf will still work fine for them, and changes will still trickle down to them. Thanks, Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org> To: Michael Ellerman <mpe@ellerman.id.au> Cc: Arnaldo Carvalho de Melo <acme@infradead.org>, ak@linux.intel.com, Peter Zijlstra <a.p.zijlstra@chello.nl>, peterz@infradead.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, mingo@redhat.com, namhyung@kernel.org, Thomas Gleixner <tglx@linutronix.de>, Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>, Jiri Olsa <jolsa@redhat.com>, Pekka Enberg <penberg@iki.fi> Subject: Re: 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.) Date: Tue, 14 Apr 2015 14:58:22 +0200 [thread overview] Message-ID: <20150414125822.GA32761@gmail.com> (raw) In-Reply-To: <1429010508.27414.1.camel@ellerman.id.au> * Michael Ellerman <mpe@ellerman.id.au> wrote: > On Tue, 2015-04-14 at 10:55 +0200, Ingo Molnar wrote: > > * Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> wrote: > > > > > This is another attempt to resurrect Andi Kleen's patchset so users > > > can specify perf events by their event names rather than raw codes. > > > > > > This is a rebase of Andi Kleen's patchset from Jul 30, 2014[1] to 4.0. > > > (I fixed minor and not so minor conflicts). > > > > So this series shows some progress, but instead of this limited > > checkout ability I'd still prefer it if 'perf download' downloaded > > the latest perf code itself and built it - it shouldn't be limited > > to just a small subset of the perf source code! > > Ingo, can you please stop blocking this? It's getting ridiculous. > > We've been waiting over 8 months for this to go in. We just merged a patch series that was first sent in 2013. Some things take time to get right. > While we've been waiting most of our users have learnt to use operf > instead, which doesn't require raw codes. > > I would also add that exactly zero users have asked for a feature > where perf downloads and rebuilds itself. In fact many of them would > consider that a security breach. Fetching tracing scripts, plugins or other instrumentation scripts can be considered a 'security breach' as well. Fetching external tables (or network access to begin with) can be considered a 'security breach' as well, depending on how restricted an environment is. But we don't design our code based on the most restrictive environments that are hostile to open source concepts! Unfortunate users that are not allowed to update open source code that they are using should probably not update it. The other 99.9% of perf users would benefit from a properly done upgrading/updating feature. Please stop thinking in terms of restricted, closed environments. Packaged perf will still work fine for them, and changes will still trickle down to them. Thanks, Ingo
next prev parent reply other threads:[~2015-04-14 12:58 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-14 6:40 [PATCH v9 00/11] Add support for JSON event files Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:40 ` [PATCH v9 01/11] perf, tools: Add jsmn `jasmine' JSON parser Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:40 ` [PATCH v9 02/11] perf, tools: Add support for text descriptions of events and alias add Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:40 ` [PATCH v9 03/11] perf, tools, list: Update perf list to output descriptions Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:40 ` [PATCH v9 04/11] perf, tools: Add support for reading JSON event files Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:40 ` [PATCH v9 05/11] perf, tools: Automatically look for event file name for cpu Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:40 ` [PATCH v9 06/11] powerpc/perf: Implement get_cpu_str() Sukadev Bhattiprolu 2015-04-14 6:40 ` Sukadev Bhattiprolu 2015-04-14 6:41 ` [PATCH v9 07/11] perf, tools: Query terminal width and use in perf list Sukadev Bhattiprolu 2015-04-14 6:41 ` Sukadev Bhattiprolu 2015-04-14 6:41 ` [PATCH v9 08/11] perf, tools: Add a new pmu interface to iterate over all events Sukadev Bhattiprolu 2015-04-14 6:41 ` Sukadev Bhattiprolu 2015-04-14 6:41 ` [PATCH v9 09/11] perf, tools, test: Add test case for alias and JSON parsing Sukadev Bhattiprolu 2015-04-14 6:41 ` Sukadev Bhattiprolu 2015-04-14 6:41 ` [PATCH v9 10/11] perf, tools: Add a --no-desc flag to perf list Sukadev Bhattiprolu 2015-04-14 6:41 ` Sukadev Bhattiprolu 2015-04-14 6:41 ` [PATCH v9 11/11] perf-download: Download the events json file Sukadev Bhattiprolu 2015-04-14 6:41 ` Sukadev Bhattiprolu 2015-04-14 8:55 ` 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.) Ingo Molnar 2015-04-14 8:55 ` Ingo Molnar 2015-04-14 11:21 ` Michael Ellerman 2015-04-14 11:21 ` Michael Ellerman 2015-04-14 12:58 ` Ingo Molnar [this message] 2015-04-14 12:58 ` Ingo Molnar 2015-04-14 18:03 ` Sukadev Bhattiprolu 2015-04-14 18:03 ` Sukadev Bhattiprolu 2015-04-14 22:53 ` Michael Ellerman 2015-04-14 22:53 ` Michael Ellerman 2015-04-15 9:25 ` Ingo Molnar 2015-04-15 9:25 ` Ingo Molnar 2015-04-15 19:17 ` Andi Kleen 2015-04-15 19:17 ` Andi Kleen 2015-04-15 20:50 ` Sukadev Bhattiprolu 2015-04-15 20:50 ` Sukadev Bhattiprolu 2015-04-17 15:31 ` Jiri Olsa 2015-04-17 15:31 ` Jiri Olsa 2015-04-17 20:09 ` Andi Kleen 2015-04-17 20:09 ` Andi Kleen 2015-04-18 13:05 ` Jiri Olsa 2015-04-18 13:05 ` Jiri Olsa 2015-04-18 13:12 ` Jiri Olsa 2015-04-18 13:12 ` Jiri Olsa 2015-04-14 20:16 ` Andi Kleen 2015-04-14 20:16 ` Andi Kleen
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=20150414125822.GA32761@gmail.com \ --to=mingo@kernel.org \ --cc=a.p.zijlstra@chello.nl \ --cc=acme@infradead.org \ --cc=acme@kernel.org \ --cc=ak@linux.intel.com \ --cc=jolsa@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mingo@redhat.com \ --cc=mpe@ellerman.id.au \ --cc=namhyung@kernel.org \ --cc=penberg@iki.fi \ --cc=peterz@infradead.org \ --cc=sukadev@linux.vnet.ibm.com \ --cc=tglx@linutronix.de \ --cc=torvalds@linux-foundation.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.