mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Yang Jihong <yangjihong1@huawei.com>,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, namhyung@kernel.org, irogers@google.com,
	kan.liang@linux.intel.com, james.clark@arm.com,
	tmricht@linux.ibm.com, ak@linux.intel.com,
	anshuman.khandual@arm.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 7/7] perf test: Add perf_event_attr test for record selected CPUs exclude_user
Date: Fri, 4 Aug 2023 10:08:04 +0300	[thread overview]
Message-ID: <e81628fb-0b6d-ccd4-97a4-3afe09159ec4@intel.com> (raw)
In-Reply-To: <20230804020741.99806-8-yangjihong1@huawei.com>

On 4/08/23 05:07, Yang Jihong wrote:
> If all (non-dummy) evsel have exclude_user, system_wide sideband is not
> needed. Add this test scenario.
> 
> Test result:
> 
>   # ./perf test list 2>&1 | grep 'Setup struct perf_event_attr'
>    17: Setup struct perf_event_attr
>   # ./perf test 17 -v
>    17: Setup struct perf_event_attr                                    :
>   --- start ---
>   test child forked, pid 720198
>   <SNIP>
>   running './tests/attr/test-record-C0-all-kernel'
>   <SNIP>
>   test child finished with 0
>   ---- end ----
>   Setup struct perf_event_attr: Ok
> 
> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>

Tested-by: Adrian Hunter <adrian.hunter@intel.com>

> ---
>  .../perf/tests/attr/test-record-C0-all-kernel | 32 +++++++++++++++++++
>  1 file changed, 32 insertions(+)
>  create mode 100644 tools/perf/tests/attr/test-record-C0-all-kernel
> 
> diff --git a/tools/perf/tests/attr/test-record-C0-all-kernel b/tools/perf/tests/attr/test-record-C0-all-kernel
> new file mode 100644
> index 000000000000..2d7549277c1e
> --- /dev/null
> +++ b/tools/perf/tests/attr/test-record-C0-all-kernel
> @@ -0,0 +1,32 @@
> +[config]
> +command = record
> +args    = --no-bpf-event --all-kernel -C 0 kill >/dev/null 2>&1
> +ret     = 1
> +
> +[event:base-record]
> +cpu=0
> +
> +# no enable on exec for CPU attached
> +enable_on_exec=0
> +
> +# PERF_SAMPLE_IP | PERF_SAMPLE_TID | PERF_SAMPLE_TIME |
> +# PERF_SAMPLE_PERIOD | PERF_SAMPLE_IDENTIFIER
> +# + PERF_SAMPLE_CPU added by -C 0
> +sample_type=65927
> +
> +# Dummy event handles mmaps, comm and task.
> +mmap=0
> +comm=0
> +task=0
> +
> +# exclude_user for all-kernel option
> +exclude_user=1
> +
> +[event:system-wide-dummy]
> +
> +# system_wide is not need for all (non-dummy) events have exclude_user
> +cpu=0
> +
> +# exclude_user for all-kernel option
> +exclude_user=1
> +exclude_kernel=0


      reply	other threads:[~2023-08-04  7:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  2:07 [PATCH v5 0/7] perf record: Track sideband events for all CPUs when tracing selected CPUs Yang Jihong
2023-08-04  2:07 ` [PATCH v5 1/7] perf evlist: Add perf_evlist__go_system_wide() helper Yang Jihong
2023-08-04  6:57   ` Adrian Hunter
2023-08-04  2:07 ` [PATCH v5 2/7] perf evlist: Add evlist__findnew_tracking_event() helper Yang Jihong
2023-08-04  6:58   ` Adrian Hunter
2023-08-04  2:07 ` [PATCH v5 3/7] perf record: Move setting dummy tracking before record__init_thread_masks() Yang Jihong
2023-08-04  6:58   ` Adrian Hunter
2023-08-14 20:29     ` Ian Rogers
2023-08-15  1:57       ` Yang Jihong
2023-08-17 12:27         ` Yang Jihong
2023-08-04  2:07 ` [PATCH v5 4/7] perf record: Track sideband events for all CPUs when tracing selected CPUs Yang Jihong
2023-08-04  6:59   ` Adrian Hunter
2023-08-04  2:07 ` [PATCH v5 5/7] perf test: Update base-record & system-wide-dummy attr expected values for test-record-C0 Yang Jihong
2023-08-04  7:00   ` Adrian Hunter
2023-08-04  2:07 ` [PATCH v5 6/7] perf test: Add test case for record sideband events Yang Jihong
2023-08-04  7:07   ` Adrian Hunter
2023-08-04  2:07 ` [PATCH v5 7/7] perf test: Add perf_event_attr test for record selected CPUs exclude_user Yang Jihong
2023-08-04  7:08   ` Adrian Hunter [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=e81628fb-0b6d-ccd4-97a4-3afe09159ec4@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anshuman.khandual@arm.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.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=tmricht@linux.ibm.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

all inboxes | Powered by JetHome®