Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp539700ybi; Fri, 7 Jun 2019 12:16:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqwy1CetmZg87bCkJ56TtjkM1WjYxqZr03zqLNfbFz9RBNfADNclj4wmOUXnClzFjNCf61je X-Received: by 2002:a17:902:d701:: with SMTP id w1mr51728201ply.12.1559935000114; Fri, 07 Jun 2019 12:16:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559935000; cv=none; d=google.com; s=arc-20160816; b=hyBZK1p7a7wxqYQFRskhDz6Ap5KDhRlJAAaNIz0L1OiQM+BPph3FOBNgb7xKfNdN0+ QPSJ9PGVEhc8L2O7xJmICqwCVtoOzT/YEDBZ4RvbBeDLP5kCWq9Yip0F4n9+1E6F8lxP vIFA3v+GMRJPOf2PuT+pUubsfwZ0G6g1qeGY+7Vfbczt1VqhBCz2EHOGca0Z1OTI37gU XQ/vFh2hb2JHUXetisJITmHPxu9Yi+mvF0SZc0c+f9AcepV3Y5CdNFMmfMN9f+bHeSnq 7L0zb9QGQ/xLlekLborKfk64PQqpWICgwTvTySX41RP+aXueHm52FJ25oSsI+qy3//Ga wU5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=ewMHrbrVvN4gVJpFfne3Ko4Ig9zBbFgoDweVZi80Iis=; b=ROMIVrV3ZY0c1YWlJjttRfB53iZf8HhOOUSgajvcEuEdDdKpbw/ESre22IyFpq644P IeiG9KqIVKy4GcBhvb6EKAbrYwV3BwBvHSgg/Yxr4KzAiabbuEriEqnZfF/EB21M7hqF Wv/7tjMiol4EKIl9iKsh7tHYvCVvgQT1vRJ6mbssXiCB1c3HeadGL4nPuGLuK0KT2J6d VuJGJQK0tczPCP8LoSl2fgGD3K3m/5zv739TJUz6f5x4hz/dMhpFCGWm4TCpFLb/or8v 8TA98WLenCP9v9RN6+N18Fg2ULtmXIXywHpgzs3ifHzxytKktIO/IBCSPKojCmkhlO3j Pf1A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ikGOtCEI; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c17si2651703pls.411.2019.06.07.12.16.22; Fri, 07 Jun 2019 12:16:40 -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=@linaro.org header.s=google header.b=ikGOtCEI; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731014AbfFGP7K (ORCPT + 99 others); Fri, 7 Jun 2019 11:59:10 -0400 Received: from mail-io1-f67.google.com ([209.85.166.67]:42656 "EHLO mail-io1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730071AbfFGP7G (ORCPT ); Fri, 7 Jun 2019 11:59:06 -0400 Received: by mail-io1-f67.google.com with SMTP id u19so1786962ior.9 for ; Fri, 07 Jun 2019 08:59:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ewMHrbrVvN4gVJpFfne3Ko4Ig9zBbFgoDweVZi80Iis=; b=ikGOtCEI2xkGJiF/rscqmIZGgmjsg2cG96nsYnWF+sShH8/2RPNrrxDEzNKw5puBJr CLnGqRjFGkyn7RGCJNhNxASebmtvirIhbTGFy8yS8IHJlPT1QYZkh3YI/fnCzw3C3oXE f3zJsVCqynVuZvcKa3O2bzpUsWxceyOPmQaQllIEX2yNH5I7Zj9/HcFMj7HbHPFEpwnG xbZ9PFiITzvbQARLu7xHvWWMXXixHxg1c8wkFzVpkPv/K2baTapbCa7nUoSVsxFPrOwY AZzZF1hlR0aZP0pb91FILI3U5DLWoL9NX6ga0IYnsPws9Y9Uhxpl/G21jCOVJ5hoORYA 1W+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ewMHrbrVvN4gVJpFfne3Ko4Ig9zBbFgoDweVZi80Iis=; b=epvts2z6DCuKzCjVq5lUkdqAftjUerMxV5Mz0rCUZo8ShUEj8WDl8+BgYmCGdGghfR 7IINTyV9gz6AjYsbmzqqc0ZgGVBhyqdPNCA5Gu6hL60VsHiT+iJfKQ1CLUpGOFycZyFR tf7Pa6VdyHudMP7dS4oLPnbBFhJ2VX9jNLvz41+JntO0bjNcXuWoijlPhN/fjaYJxpj0 P3+D5uLpYv+dzkTUzCArOYEDaoaV9z2TIxlGd+b3RuyqxGvMh35jgNRydtBj6cYWJz2u qNHqvoDaOg5ynK5Qc/ZqOIzDY4pFD9wpZl+8NwZuV3OqNfUNRCfsblUrazY8rslwQEfJ VlWA== X-Gm-Message-State: APjAAAUa3RsQYSg/EepfFIOdilPgro6yMfaa6T29eGsUfA372mghDpdR QWECEATq5Cpu2xoqXWVhOfQWdY4MauxQ5ZzQUs4/rhDy X-Received: by 2002:a6b:2c96:: with SMTP id s144mr19148570ios.57.1559923145932; Fri, 07 Jun 2019 08:59:05 -0700 (PDT) MIME-Version: 1.0 References: <1559229077-26436-1-git-send-email-suzuki.poulose@arm.com> <20190603190133.GA20462@xps15> <99055755-6525-694e-a15d-5de7318a80da@arm.com> <20190607022136.GE5970@leoy-ThinkPad-X240s> <78c98c28-4f3f-825b-18e1-c71fb63a80eb@arm.com> In-Reply-To: <78c98c28-4f3f-825b-18e1-c71fb63a80eb@arm.com> From: Mathieu Poirier Date: Fri, 7 Jun 2019 09:58:54 -0600 Message-ID: Subject: Re: [PATCH] Documentation: coresight: Update the generic device names To: Suzuki K Poulose Cc: Leo Yan , linux-arm-kernel , Linux Kernel Mailing List , Coresight ML , Jon Corbet Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 7 Jun 2019 at 02:40, Suzuki K Poulose wrote: > > Hi Leo, > > >>>> A Coresight PMU works the same way as any other PMU, i.e the name of the PMU is > >>>> listed along with configuration options within forward slashes '/'. Since a > >>>> Coresight system will typically have more than one sink, the name of the sink to > >>>> -work with needs to be specified as an event option. Names for sink to choose > >>>> -from are listed in sysFS under ($SYSFS)/bus/coresight/devices: > >>>> +work with needs to be specified as an event option. > >>>> +On newer kernels the available sinks are listed in sysFS under: > >>>> +($SYSFS)/bus/event_source/devices/cs_etm/sinks/ > >>>> - root@linaro-nano:~# ls /sys/bus/coresight/devices/ > >>>> - 20010000.etf 20040000.funnel 20100000.stm 22040000.etm > >>>> - 22140000.etm 230c0000.funnel 23240000.etm 20030000.tpiu > >>>> - 20070000.etr 20120000.replicator 220c0000.funnel > >>>> - 23040000.etm 23140000.etm 23340000.etm > >>>> + root@localhost:/sys/bus/event_source/devices/cs_etm/sinks# ls > >>>> + tmc_etf0 tmc_etr0 tpiu0 > >>>> - root@linaro-nano:~# perf record -e cs_etm/@20070000.etr/u --per-thread program > >>>> +On older kernels, this may need to be found from the list of coresight devices, > >>>> +available under ($SYSFS)/bus/coresight/devices/: > >>>> + > >>>> + root@localhost:/sys/bus/coresight/devices# ls > >>>> + etm0 etm1 etm2 etm3 etm4 etm5 funnel0 funnel1 funnel2 replicator0 stm0 tmc_etf0 tmc_etr0 tpiu0 > >>>> + > >>>> + root@linaro-nano:~# perf record -e cs_etm/@tmc_etr0/u --per-thread program > >>> > >>> On the "older" kernels you are referring to one would find the original naming > >>> convention. Everything else looks good to me. > >> > >> True, but do we care what we see there ? All we care about is the location, > >> where to find them. I could fix it, if you think thats needed. > > > > IIUC, either the old kernel or newer kernel, both we can find the event > > from ($SYSFS)/bus/event_source/devices/cs_etm/sinks/; the only > > difference between them is the naming convention. > > The cs_etm/sinks was only added with the CPU-wide trace support. So, if someone > refers to this document alone and then tries to do something on on older kernel, > which is quite possible for a production device running a stable kernel, {s,}he > might be surprised. > > > > > So the doc can use the same location to find event for both new and > > old kernel, and explain the naming convention difference? > > My question is really, does the naming convention matter ? What you see > under the directory is the name. But yes, I am open to add a section to > explain the fact that we changed the naming scheme, if everyone agrees > to it. I think it would be preferable to mention the change - just a small section that describes what happened and the reason for doing so will be fine. > > Cheers > Suzuki