Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp415808pxx; Mon, 26 Oct 2020 11:23:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwDOTAhnUrkE2hDR1/6CnuM5gYl/W+mnKjz3mVxg1q8E/oiEcYdSqvThaI4M6l3Xtpqcw0h X-Received: by 2002:a05:6402:1201:: with SMTP id c1mr17278800edw.210.1603736580662; Mon, 26 Oct 2020 11:23:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603736580; cv=none; d=google.com; s=arc-20160816; b=syAzH6/b7cQHTkqMe/yYYshfvxym+ygNqAu+Ub5bT4LZlM8nOTAiKnUYAy1BP+7mWv OW41ZlAm6MAUalfesQ3w42osBqWSLNIupwEry+6J/1KjbBzRYBhtGsgJYVsrqLZUA/lC 6FGb1ZCX3fk3ASz8Ck5bdznv0EknSUlgISjZLsDFTZq7Wlej6fa5sn2eK+GAOjL+j6mu pj+VOrH1yHZr9iS4/4PvjyW9EsB6sbntpfIYe3z53jTnsOaK5Htzd15bNx7khl79+GNn rY4vCZAd0v7jwhJG0XW3WWJazRgn97zeyPGwQXzbXFP0+mMXFRgZFaA5+vmUTeyBugzJ uydw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:ironport-sdr:ironport-sdr; bh=Hxs3aY2rUlJVcZBVM6mUn348kzL+esQ/QpuRg93U0X8=; b=VYhAbPAqMtNPwIukj0Cwmm78DUYSfCvRWwvYDNmeKwVT04X132vvqQJANpVLkA1KiK Q8h13c2sNeGQ8ZzTxHlo1HxcI1qE88fkugtfQ2RDASnaoQ3Ly4xj0PCoCVtXaILuYiF+ b49zSJJZimT3Enp+tvN1CppJCngvtdQo3jw4Dt6f6OzOCJl9lI0sCSPbauzHFCK+ZlaE SCcYd8uv0XaYAj5VinYKJQkIyCtcNADCZ1xD8WbI8n8bEeR4E5+nMns+/gC3zkvJCjiA kOwt5LrqnBLcWH2vpkiQivScKgTTeD60LLNX01J5WN1ctHSC9All0HeBhdsKAn8Bqjxz 37+Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l6si7417317eds.406.2020.10.26.11.22.38; Mon, 26 Oct 2020 11:23:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1784401AbgJZPtP (ORCPT + 99 others); Mon, 26 Oct 2020 11:49:15 -0400 Received: from mga03.intel.com ([134.134.136.65]:34210 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1773092AbgJZPtP (ORCPT ); Mon, 26 Oct 2020 11:49:15 -0400 IronPort-SDR: Qx6XNKoNK4y9Gcprj6v/AEH2VaFZQGBRZoOkOnWz4m9cgfjyM7imqfK6+s82wqXytg64kPpfKz pYmbuy9KjyLw== X-IronPort-AV: E=McAfee;i="6000,8403,9786"; a="168041448" X-IronPort-AV: E=Sophos;i="5.77,420,1596524400"; d="scan'208";a="168041448" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Oct 2020 08:49:11 -0700 IronPort-SDR: L8CHJOf2wvavRphnAa7lRq33t4OuN8POPsrsN04+1wsbgVoo/uMvtCu3d61iojK6cLpyXh36vx 28L2YFSY/uRA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,420,1596524400"; d="scan'208";a="467967505" Received: from um.fi.intel.com (HELO um) ([10.237.72.57]) by orsmga004.jf.intel.com with ESMTP; 26 Oct 2020 08:49:08 -0700 From: Alexander Shishkin To: Andi Kleen , Namhyung Kim Cc: Arnaldo Carvalho de Melo , Jiri Olsa , Peter Zijlstra , Ingo Molnar , Mark Rutland , LKML , Stephane Eranian , Ian Rogers , alexander.shishkin@linux.intel.com Subject: Re: [RFC] perf evlist: Warn if event group has mixed sw/hw events In-Reply-To: <20201026152108.GW466880@tassilo.jf.intel.com> References: <20201026141937.582087-1-namhyung@kernel.org> <20201026152108.GW466880@tassilo.jf.intel.com> Date: Mon, 26 Oct 2020 17:49:07 +0200 Message-ID: <87y2jtq970.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andi Kleen writes: > On Mon, Oct 26, 2020 at 11:19:37PM +0900, Namhyung Kim wrote: >> This patch just added a warning before running it. I'd really want to >> fix the kernel if possible but don't have a good idea. Thoughts? > > The easiest fix would be some multi threading in perf stat opening, then then > extra latencies could be mostly hidden. One thread per group would probably > be overkill, but just a few threads would lower the penalty significantly. > > I think that would be better than this patch and it's likely not that much > more complicated, as this is already a lot of code. > >> +{ >> + const char *known_sw_pmu[] = { >> + "software", "tracepoint", "breakpoint", "kprobe", "uprobe", "msr" > > That's a non scalable approach. New pmus get added regularly. It would be better to > indicate this in a generic way from the kernel. That, and also, intel_pt is a software PMU and a few of its features depend on intel_pt/.../ being a group leader. Regards, -- Alex