Linux Perf Users
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: acme@kernel.org, irogers@google.com, peterz@infradead.org,
	mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	adrian.hunter@intel.com, kan.liang@linux.intel.com,
	yangjihong1@huawei.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, sandipan.das@amd.com,
	ananth.narayan@amd.com, santosh.shukla@amd.com,
	Stephane Eranian <eranian@google.com>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [PATCH] perf doc: Add AMD IBS usage document
Date: Wed, 19 Jun 2024 21:26:34 +0530	[thread overview]
Message-ID: <0b53607e-03f4-4f3e-9332-c9f4c43ac88b@amd.com> (raw)
In-Reply-To: <CAM9d7chpM4k+BRNNf6V0OS1PRX7c9f+QXa0EwKWjPPzAZVYZBw@mail.gmail.com>

>> +IBS Fetch PMU
>> +~~~~~~~~~~~~~
>> +
>> +Similar commands can be used with Fetch PMU as well.
>> +
>> +System-wide profile, fetch ops event, sampling period: 100000
>> +
>> +       $ sudo perf record -e ibs_fetch// -c 100000 -a
>> +
>> +System-wide profile, fetch ops event, sampling period: 100000, Random enable
> 
> Can you please add a brief description of what 'random enable' means?

Sure, here is the detail about RandEn bit:

Sample period value in IBS Fetch PMU must be multiple of 16. IBS hardware
internally sets pseudo-random value in [3:0] bits when RandEn bit is set.
This variability will help in cases like long running loops where IBS
Fetch PMU is tagging the same instruction over and over because of the
fixed sample period.

Thanks for the review,
Ravi

      reply	other threads:[~2024-06-19 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  9:22 [PATCH] perf doc: Add AMD IBS usage document Ravi Bangoria
2024-06-19 13:28 ` Arnaldo Carvalho de Melo
2024-06-19 15:39   ` Ravi Bangoria
2024-06-19 14:51 ` Namhyung Kim
2024-06-19 15:56   ` Ravi Bangoria [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0b53607e-03f4-4f3e-9332-c9f4c43ac88b@amd.com \
    --to=ravi.bangoria@amd.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth.narayan@amd.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sandipan.das@amd.com \
    --cc=santosh.shukla@amd.com \
    --cc=yangjihong1@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox