From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754331AbbDNUQx (ORCPT ); Tue, 14 Apr 2015 16:16:53 -0400 Received: from mga09.intel.com ([134.134.136.24]:36944 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753833AbbDNUQo (ORCPT ); Tue, 14 Apr 2015 16:16:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,577,1422950400"; d="scan'208";a="713644646" Date: Tue, 14 Apr 2015 13:16:43 -0700 From: Andi Kleen To: Ingo Molnar Cc: Sukadev Bhattiprolu , mingo@redhat.com, Michael Ellerman , Jiri Olsa , Arnaldo Carvalho de Melo , peterz@infradead.org, namhyung@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Pekka Enberg , Arnaldo Carvalho de Melo , Peter Zijlstra , Thomas Gleixner Subject: Re: 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.) Message-ID: <20150414201643.GY15335@tassilo.jf.intel.com> References: <1428993665-2133-1-git-send-email-sukadev@linux.vnet.ibm.com> <20150414085541.GA30202@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150414085541.GA30202@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 14, 2015 at 10:55:41AM +0200, Ingo Molnar wrote: > > * Sukadev Bhattiprolu 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! I'm not against that idea (and can see it being useful in some cases[1]), but this would need some authentication. Otherwise it would be a "$bigbrother/nsa/anyone controling your network can run everything on your computer" style hole. The original JSON files don't have this problem because they didn't contain any code. -Andi [1] especially to work around the broken perf setup on d./u. distros. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lists.ozlabs.org (Postfix) with ESMTP id 44F891A0143 for ; Wed, 15 Apr 2015 06:16:45 +1000 (AEST) Date: Tue, 14 Apr 2015 13:16:43 -0700 From: Andi Kleen To: Ingo Molnar Subject: Re: 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.) Message-ID: <20150414201643.GY15335@tassilo.jf.intel.com> References: <1428993665-2133-1-git-send-email-sukadev@linux.vnet.ibm.com> <20150414085541.GA30202@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20150414085541.GA30202@gmail.com> Cc: Arnaldo Carvalho de Melo , Peter Zijlstra , peterz@infradead.org, linuxppc-dev@lists.ozlabs.org, Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, mingo@redhat.com, namhyung@kernel.org, Thomas Gleixner , Sukadev Bhattiprolu , Jiri Olsa , Pekka Enberg List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Apr 14, 2015 at 10:55:41AM +0200, Ingo Molnar wrote: > > * Sukadev Bhattiprolu 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! I'm not against that idea (and can see it being useful in some cases[1]), but this would need some authentication. Otherwise it would be a "$bigbrother/nsa/anyone controling your network can run everything on your computer" style hole. The original JSON files don't have this problem because they didn't contain any code. -Andi [1] especially to work around the broken perf setup on d./u. distros.