All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	James Clark <james.clark@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf arm-spe: Report error if set frequency
Date: Wed, 26 Feb 2025 23:05:08 -0800	[thread overview]
Message-ID: <Z8AOpLW6RSUU09Ns@google.com> (raw)
In-Reply-To: <20250217082008.GA8144@e132581.arm.com>

Hello,

On Mon, Feb 17, 2025 at 08:20:08AM +0000, Leo Yan wrote:
> On Wed, Feb 05, 2025 at 06:30:09PM +0000, Leo Yan wrote:
> > When users set the parameter '-F' to specify frequency for Arm SPE, the
> > tool reports error:
> > 
> >   perf record -F 1000 -e arm_spe_0// -- sleep 1
> >   Error:
> >   Invalid event (arm_spe_0//) in per-thread mode, enable system wide with '-a'.
> > 
> > The output logs are confused and it does not give the correct reminding.
> > Arm SPE does not support frequency setting given it adopts a statistical
> > based approach.
> > 
> > Alternatively, Arm SPE supports setting period.  This commit adds a
> > for frequency setting.  It reports error and reminds users to set period
> > instead.
> > 
> > After:
> > 
> >   perf record -F 100 -e arm_spe_0// -- sleep 1
> >   Arm SPE: Frequency is not supported. Check manual 'man perf-record' on how to set period.
> > 
> > Signed-off-by: Leo Yan <leo.yan@arm.com>
> 
> Gentle ping.

Sorry for the late reply.

Isn't it just -c <period> to set period for Arm SPE?  If so, it'd be
better to say that explicitly.

Thanks,
Namhyung

> 
> > ---
> >  tools/perf/arch/arm64/util/arm-spe.c | 20 ++++++++++++++++++++
> >  1 file changed, 20 insertions(+)
> > 
> > diff --git a/tools/perf/arch/arm64/util/arm-spe.c b/tools/perf/arch/arm64/util/arm-spe.c
> > index 4301181b8e45..baef0812dc19 100644
> > --- a/tools/perf/arch/arm64/util/arm-spe.c
> > +++ b/tools/perf/arch/arm64/util/arm-spe.c
> > @@ -40,6 +40,19 @@ struct arm_spe_recording {
> >  	bool			*wrapped;
> >  };
> >  
> > +/* Iterate config list to detect if the "freq" parameter is set */
> > +static bool arm_spe_is_set_freq(struct evsel *evsel)
> > +{
> > +	struct evsel_config_term *term;
> > +
> > +	list_for_each_entry(term, &evsel->config_terms, list) {
> > +		if (term->type == EVSEL__CONFIG_TERM_FREQ)
> > +			return true;
> > +	}
> > +
> > +	return false;
> > +}
> > +
> >  /*
> >   * arm_spe_find_cpus() returns a new cpu map, and the caller should invoke
> >   * perf_cpu_map__put() to release the map after use.
> > @@ -389,6 +402,13 @@ static int arm_spe_recording_options(struct auxtrace_record *itr,
> >  				return -EINVAL;
> >  			}
> >  			opts->full_auxtrace = true;
> > +
> > +			if (opts->user_freq != UINT_MAX ||
> > +			    arm_spe_is_set_freq(evsel)) {
> > +				pr_err("Arm SPE: Frequency is not supported. "
> > +				       "Check manual 'man perf-record' on how to set period.\n");
> > +				return -EINVAL;
> > +			}
> >  		}
> >  	}
> >  
> > -- 
> > 2.34.1
> > 


  reply	other threads:[~2025-02-27  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 18:30 [PATCH] perf arm-spe: Report error if set frequency Leo Yan
2025-02-17  8:20 ` Leo Yan
2025-02-27  7:05   ` Namhyung Kim [this message]
2025-02-27  8:22     ` Leo Yan

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=Z8AOpLW6RSUU09Ns@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=leo.yan@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.