Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp709384ybh; Wed, 11 Mar 2020 09:14:38 -0700 (PDT) X-Google-Smtp-Source: ADFU+vtEklIeys/pYRiAei5Pb7+0xXnZDrDEx7ZFPVxAQ8O4FiDhdTC/T8pMTH9TA7dddrMpR0Vj X-Received: by 2002:a9d:6251:: with SMTP id i17mr3027464otk.14.1583943278217; Wed, 11 Mar 2020 09:14:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583943278; cv=none; d=google.com; s=arc-20160816; b=hT8d4Ib2sim52KRFMwPXnGntTre7gl3ANnKIPzo+hSj+z44cCUdWrZCDWaQyEGkbb/ JY8AOIf8jW1ptPLInkOPkyahSGRPiZCNxC+GkUfuD7er0BtZOQWEl3gH9FsR1R+0d1b3 iecnfm+aWZo7Fu8Yp2YZ8ir0b0dBTsRxF4+sADEtRigA6Np+k8gU/9x1mmqac9HXjRvs rBqz7on0w9LC9PohgeklReQzpLMtFwHtmTtVByoX1PGSkbBtfuxGBmhZt4QoZqzONHOa dbm9blnNAoBUVsFDtmOjrgts3GGhMeo20KPwM0bKtRAY8/XDG07QpqoY/+sZrrUnd1c+ c0Nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=C2dn7dDfcp/5qsKW13nLYAsv37ZI1/+LekwqWkQ/smk=; b=eG/8bzmIbDNckRD+70+HR7wdUWb7V78IlP5keX9AqxeyXlmXUMTpV15ci30xmdMKzk RQwaor41nxJAH4blcpxEs7fE3OgOyP5odQZ/VRjUPCQG52hkHAklbMcvqh6AICHbdCQt lxVJPqjx3B/s27Mh5OndkA1Eawv2oiSFA2YJXI52cYVDtrOGZe56qCfIz1mtj4BBlVOj FkX09llDAfNPvRwzY3Xt0c4QCcwCJPDCtr4q92KL6Xj53sW8aWwDHaVQ/qmaxa066Cc0 iOITNyi4WgOVnKT7GjR8yrmCnyd5z/GEMjyvlqDEfvX/1eXP7kJzpJZWeXbBwo/462wl 2Mug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=I9JKLmSF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i124si1371402oib.172.2020.03.11.09.14.20; Wed, 11 Mar 2020 09:14:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=I9JKLmSF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730271AbgCKQN4 (ORCPT + 99 others); Wed, 11 Mar 2020 12:13:56 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:21990 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730264AbgCKQNz (ORCPT ); Wed, 11 Mar 2020 12:13:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1583943234; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=C2dn7dDfcp/5qsKW13nLYAsv37ZI1/+LekwqWkQ/smk=; b=I9JKLmSF1R3Z6P3yNFBr+t4ohbGFCb2ZpG5W2xAd+JFwnSqydyo9fCzsDuMMtAyPvM0rbh gbqXHJxbFPqBvnSzztln52ZYlkE34uB+UpVUIaE8ae+NMDaEKu46kJzH8kB1DQ44LaztS8 pEHAfxWId0WwvFpfHWzxzZVMsdgIBQ4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-152-31R9xhpePXm_8X4A4fDqgQ-1; Wed, 11 Mar 2020 12:13:45 -0400 X-MC-Unique: 31R9xhpePXm_8X4A4fDqgQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 37D8CDB21; Wed, 11 Mar 2020 16:13:42 +0000 (UTC) Received: from krava (ovpn-204-40.brq.redhat.com [10.40.204.40]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 06C818F354; Wed, 11 Mar 2020 16:13:34 +0000 (UTC) Date: Wed, 11 Mar 2020 17:13:20 +0100 From: Jiri Olsa To: Stephane Eranian Cc: Andi Kleen , Ian Rogers , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Namhyung Kim , Alexei Starovoitov , Daniel Borkmann , Martin KaFai Lau , Yonghong Song , Andrii Nakryiko , Greg Kroah-Hartman , Thomas Gleixner , Igor Lubashev , Alexey Budankov , Florian Fainelli , Adrian Hunter , Jiwei Sun , yuzhoujian , Kan Liang , Jin Yao , Leo Yan , John Garry , LKML , netdev@vger.kernel.org, bpf@vger.kernel.org, linux-perf-users@vger.kernel.org Subject: Re: [PATCH] perf tools: add support for lipfm4 Message-ID: <20200311161320.GA254105@krava> References: <20200310185003.57344-1-irogers@google.com> <20200310195915.GA1676879@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 10, 2020 at 02:39:23PM -0700, Stephane Eranian wrote: > On Tue, Mar 10, 2020 at 12:59 PM Andi Kleen wrote: > > > > On Tue, Mar 10, 2020 at 11:50:03AM -0700, Ian Rogers wrote: > > > This patch links perf with the libpfm4 library. > > > This library contains all the hardware event tables for all > > > processors supported by perf_events. This is a helper library > > > that help convert from a symbolic event name to the event > > > encoding required by the underlying kernel interface. This > > > library is open-source and available from: http://perfmon2.sf.net. > > > > For most CPUs the builtin perf JSON event support should make > > this redundant. > > > We decided to post this patch to propose an alternative to the JSON > file approach. It could be an option during the build. > The libpfm4 library has been around for 15 years now. Therefore, it > supports a lot of processors core and uncore and it is very portable. > The key value add I see is that this is a library that can be, and has > been, used by tool developers directly in their apps. It can > work with more than Linux perf_events interface. It is not tied to the > interface. It has well defined and documented entry points. > We do use libpfm4 extensively at Google in both the perf tool and > applications. The PAPI toolkit also relies on this library. > > I don't see this as competing with the JSON approach. It is just an > option I'd like to offer to users especially those familiar > with it in their apps. I dont mind having it, in fact I found really old email where I'm asking Peter about that ;-) and he wasn't very keen about that: https://lore.kernel.org/lkml/1312806326.10488.30.camel@twins/ not sure what was the actual reason at that time and if anything changed since.. Peter? btw I can't apply even that v2 on latest Arnaldo's branch jirka