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,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 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 F2A9DC433E0 for ; Mon, 3 Aug 2020 13:27:21 +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 BDF9C206DA for ; Mon, 3 Aug 2020 13:27:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="xlwrU6NJ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BDF9C206DA Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com 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-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=sA9m9GoaZGlnBHQMPS/JMWqgwgV/FzeY6aX9DYptCgM=; b=xlwrU6NJ+kYJRFc87Ie58AF76 jDw+Tg8bi/jsx9wetQN3b6lSyVGFDV++DFLQUkgd1JYYbVCgrWsItgRaDW/bGsHOSe+RKH6GL3VFy jUaRSbDdFZe97ajHUkZ2GhOkBFab/lW7yQU/jXkBKWeQ6OECDqKDZ5P3NlMBoBCakNJ+AWT2RSTnC w/CBvytiX6VdS9v53UkdP1KhkQxbMLZ9CFgHJ9Z/IPf8xJaAu33O/6gJ18UxBtI0EtvjTwTGc6ohW utofQS9Y6J6dqj+F6Axw3Is7Wiyt+zywuYn1Uuj0MTKvDnUtlw6LBQUKXxwL0MSiQHGIH/vFCpNBb MIaljMV3Q==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2aTe-0003lD-1k; Mon, 03 Aug 2020 13:26:06 +0000 Received: from lhrrgout.huawei.com ([185.176.76.210] helo=huawei.com) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2aTb-0003kD-7B for linux-arm-kernel@lists.infradead.org; Mon, 03 Aug 2020 13:26:04 +0000 Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id C220416D292280C7490A; Mon, 3 Aug 2020 14:26:00 +0100 (IST) Received: from [127.0.0.1] (10.210.168.55) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 3 Aug 2020 14:25:59 +0100 Subject: Re: [PATCH v2 2/2] perf pmu: Improve CPU core PMU HW event list ordering To: Arnaldo Carvalho de Melo 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> <20200803125423.GA3440834@kernel.org> From: John Garry Message-ID: <27e46a45-9055-dbb7-324e-28a65120091d@huawei.com> Date: Mon, 3 Aug 2020 14:23:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: <20200803125423.GA3440834@kernel.org> Content-Language: en-US X-Originating-IP: [10.210.168.55] X-ClientProxiedBy: lhreml726-chm.china.huawei.com (10.201.108.77) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200803_092603_463848_5B29FD25 X-CRM114-Status: GOOD ( 23.64 ) 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 03/08/2020 13:54, Arnaldo Carvalho de Melo wrote: >> 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 > If it makes sense, it could be useful to have this included in the MAINTAINERS file. That's for forgetful people like me :) > 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. ok, thanks for the detailed response. > > Arch specific kernel bits have been going via the arch trees for quite a > while, I think. > > - Arnaldo > . Cheers, john _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel