From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 61354C433E0 for ; Mon, 3 Aug 2020 12:55:53 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 336FB20678 for ; Mon, 3 Aug 2020 12:55:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="dqn3vIbe" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 336FB20678 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=e4CapM13TxahBx5+d3rRfuybZubvYI1buk2wIcTj4o4=; b=dqn3vIbejuBiNHd0vHEQcPY93 HglzyIjf5XdTYXfMzWQmgQ9ayPsz1xPe4yRzb9ApYa39b3Ue0MKjnUME4g23CZMFqdDw1T9oPmv7C VLO/fiufnkknMvQNDTXcJ/FhDX7depMEJ1OTcIx9/nWjoRWiXHLsUllxJffvwMT9ty6gKUjeRLyjZ rbyd943YQC+mugrK25Ldgcai/3Fyn23OmrKuA1lFLj8JldSowaQ3Lu76oshQhzLj2C8e2MmRC9WkN Nu9UQTlWGF1VJ/xiJ4Dzdjq2oBC1yi8ZnuUirgLv4TrV2yT0qCBSxyY/auFDV3UcIN53Q9156aB+8 PgHKhoIkQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2ZzD-0007qc-PM; Mon, 03 Aug 2020 12:54:39 +0000 Received: from [177.158.178.165] (helo=quaco.ghostprotocols.net) by merlin.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2ZzA-0007pS-FQ; Mon, 03 Aug 2020 12:54:36 +0000 Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id D615540C7C; Mon, 3 Aug 2020 09:54:23 -0300 (-03) Date: Mon, 3 Aug 2020 09:54:23 -0300 From: Arnaldo Carvalho de Melo To: John Garry Subject: Re: [PATCH v2 2/2] perf pmu: Improve CPU core PMU HW event list ordering Message-ID: <20200803125423.GA3440834@kernel.org> References: <1592384514-119954-1-git-send-email-john.garry@huawei.com> <1592384514-119954-3-git-send-email-john.garry@huawei.com> <20200617121549.GA31085@kernel.org> <74303789-6c06-574d-674b-202cf84a2018@huawei.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <74303789-6c06-574d-674b-202cf84a2018@huawei.com> X-Url: http://acmel.wordpress.com X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , Ian Rogers , Andi Kleen , Peter Zijlstra , will@kernel.org, linuxarm@huawei.com, linux-kernel , Alexander Shishkin , Ingo Molnar , Namhyung Kim , Jiri Olsa , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Em Mon, Aug 03, 2020 at 09:00:06AM +0100, John Garry escreveu: > On 17/06/2020 13:15, Arnaldo Carvalho de Melo wrote: > > Em Wed, Jun 17, 2020 at 08:31:02PM +0900, Namhyung Kim escreveu: > > > On Wed, Jun 17, 2020 at 6:06 PM John Garry wrote: > > > > For perf list, the CPU core PMU HW event ordering is such that not all > > > > events may will be listed adjacent - consider this example: > > > > cstate_pkg/c6-residency/ [Kernel PMU event] > > > > cstate_pkg/c7-residency/ [Kernel PMU event] > > > > Signed-off-by: John Garry > > > Acked-by: Namhyung Kim > > Thanks a lot, applied. > I'm struggling to understand which branch we should base our development on. > I don't see these patches in perf/core or linux-next. I saw someone > mentioned tmp.perf/core as a baseline, but I can't see that branch in > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > > Please let me know - it would be useful for any dev during the merge window. So, I'm now pushing things directly to Linus, but just the tooling part, the branch to do development on is: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core At some point I think we'll have a git/perf-tools/perf-tools.git, just like tip, but for now, please use the one above. My perf/core in the past was rebaseable, I did changes in it after publishing, trying to have solid bisectability, since I process patch by patch doing tests on it when we noticed problems, prior to pushing to Ingo for tip. Now I am making perf/core non-rebaseable, I push things there periodically, tagging what is there with the test results, see: https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/tag/?h=perf-tools-tests-2020-07-17 https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/tag/?h=perf-tools-tests-2020-07-02 I'll try and tag today's state of that tree, which I did tests already but since v5.8 was released, I merged it there and will retest and tag the test results. The tmp.perf/core one is an experiment in making what I have in my local tree available for more bleeding edge things that are being done, say in that metrics effort, etc, but I think I'll stop that, since, as your message shows, it is causing confusion. I did this because these tests take quite some time and sometimes I have to fix things and restart it, rinse, repeat. So please use: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core I'll further automate all this so that we have a more regular cadence of updates to perf/core, say every two days or so. If you have changes that touch both the kernel and userspace, the kernel bits need to go via tip, the tooling via the perf tree, that for now (well, it has been like that for quite a long time) is my tree. Arch specific kernel bits have been going via the arch trees for quite a while, I think. - Arnaldo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel