All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Stanislav Fomichev <sdf@google.com>,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: davem@davemloft.net, ast@kernel.org
Subject: Re: [PATCH bpf-next] selftests: bpf: don't depend on hardcoded perf sample_freq
Date: Mon, 25 Mar 2019 12:55:19 +0100	[thread overview]
Message-ID: <e880b488-1afb-d15e-29e2-df7940dc8def@iogearbox.net> (raw)
In-Reply-To: <20190319215324.37242-1-sdf@google.com>

On 03/19/2019 10:53 PM, Stanislav Fomichev wrote:
> When running stacktrace_build_id_nmi, try to query
> kernel.perf_event_max_sample_rate sysctl and use it as a sample_freq.
> If there was an error reading sysctl, fallback to 5000.
> 
> kernel.perf_event_max_sample_rate sysctl can drift and/or can be
> adjusted by the perf tool, so assuming a fixed number might be
> problematic on a long running machine.
> 
> Signed-off-by: Stanislav Fomichev <sdf@google.com>

Mostly trying to understand rationale a bit better in context of
selftests; perf_event_max_sample_rate could drift also after this
patch here, but I presume you are saying that the frequency we
request below would interfere too much with perf tool adjusted
one and thus affect whole rest of kernel also after selftests
finished running, so below would handle it more gracefully, right?

> ---
>  .../bpf/prog_tests/stacktrace_build_id_nmi.c     | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/bpf/prog_tests/stacktrace_build_id_nmi.c b/tools/testing/selftests/bpf/prog_tests/stacktrace_build_id_nmi.c
> index 8a114bb1c379..1c1a2f75f3d8 100644
> --- a/tools/testing/selftests/bpf/prog_tests/stacktrace_build_id_nmi.c
> +++ b/tools/testing/selftests/bpf/prog_tests/stacktrace_build_id_nmi.c
> @@ -1,13 +1,25 @@
>  // SPDX-License-Identifier: GPL-2.0
>  #include <test_progs.h>
>  
> +static __u64 read_perf_max_sample_freq(void)
> +{
> +	__u64 sample_freq = 5000; /* fallback to 5000 on error */
> +	FILE *f;
> +
> +	f = fopen("/proc/sys/kernel/perf_event_max_sample_rate", "r");
> +	if (f == NULL)
> +		return sample_freq;
> +	fscanf(f, "%llu", &sample_freq);
> +	fclose(f);
> +	return sample_freq;
> +}
> +
>  void test_stacktrace_build_id_nmi(void)
>  {
>  	int control_map_fd, stackid_hmap_fd, stackmap_fd, stack_amap_fd;
>  	const char *file = "./test_stacktrace_build_id.o";
>  	int err, pmu_fd, prog_fd;
>  	struct perf_event_attr attr = {
> -		.sample_freq = 5000,
>  		.freq = 1,
>  		.type = PERF_TYPE_HARDWARE,
>  		.config = PERF_COUNT_HW_CPU_CYCLES,
> @@ -20,6 +32,8 @@ void test_stacktrace_build_id_nmi(void)
>  	int build_id_matches = 0;
>  	int retry = 1;
>  
> +	attr.sample_freq = read_perf_max_sample_freq();
> +
>  retry:
>  	err = bpf_prog_load(file, BPF_PROG_TYPE_PERF_EVENT, &obj, &prog_fd);
>  	if (CHECK(err, "prog_load", "err %d errno %d\n", err, errno))
> 


  reply	other threads:[~2019-03-25 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 21:53 [PATCH bpf-next] selftests: bpf: don't depend on hardcoded perf sample_freq Stanislav Fomichev
2019-03-25 11:55 ` Daniel Borkmann [this message]
2019-03-25 16:46   ` Stanislav Fomichev
2019-03-26 19:49     ` Alexei Starovoitov

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=e880b488-1afb-d15e-29e2-df7940dc8def@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.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.