Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754667AbdHVHDg (ORCPT ); Tue, 22 Aug 2017 03:03:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55584 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754565AbdHVHDf (ORCPT ); Tue, 22 Aug 2017 03:03:35 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B7AEAC047B8C Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jolsa@redhat.com Date: Tue, 22 Aug 2017 09:03:32 +0200 From: Jiri Olsa To: Andi Kleen Cc: Stephane Eranian , LKML , Arnaldo Carvalho de Melo , Peter Zijlstra , "mingo@elte.hu" , "Liang, Kan" Subject: Re: [PATCH] perf record: enable multiplexing scaling via -R Message-ID: <20170822070332.GA21829@krava> References: <1503342849-2036-1-git-send-email-eranian@google.com> <87wp5wr0cb.fsf@firstfloor.org> <20170822012545.GJ2482@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170822012545.GJ2482@two.firstfloor.org> User-Agent: Mutt/1.8.3 (2017-05-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 22 Aug 2017 07:03:34 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 27 On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote: > On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote: > > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote: > > > > > > Stephane Eranian writes: > > > > > > > > To activate, the user must use: > > > > $ perf record -a -R .... > > > > > > I don't know why you're overloading the existing raw mode? > > > > > > It has nothing to do with that. > > > > > I explained this in the changelog. So that is does not change any of > > the processing in perf report, i.e., no faced with data it does not > > know how to handle. > > Also trying to avoid adding yet another option. > > But raw is needed for some of the non Intel PMUs. I believe it's > the only way to use AMD IBS. You may as well break their usage. > > You'll need a new option. I agree with Andi, I don't think we should mix those, we should have a way to switch it on/off jirka