mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: Daniel Xu <dxu@dxuuu.xyz>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	Song Liu <songliubraving@fb.com>,
	"Andrii Nakryiko" <andriin@fb.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Kernel Team <Kernel-team@fb.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH v5 bpf-next 2/2] selftests/bpf: add bpf_read_branch_records() selftest
Date: Sun, 26 Jan 2020 04:50:14 +0000	[thread overview]
Message-ID: <fcbc20dd-e5ca-e779-774f-49490dc87c3b@fb.com> (raw)
In-Reply-To: <C05FGIY6DS21.3FOPNFKMT6EWK@dlxu-fedora-R90QNFJV>



On 1/25/20 8:10 PM, Daniel Xu wrote:
> On Sat Jan 25, 2020 at 6:53 PM, Alexei Starovoitov wrote:
>> On Sat, Jan 25, 2020 at 2:32 PM Daniel Xu <dxu@dxuuu.xyz> wrote:
>>> +       attr.type = PERF_TYPE_HARDWARE;
>>> +       attr.config = PERF_COUNT_HW_CPU_CYCLES;
>>> +       attr.freq = 1;
>>> +       attr.sample_freq = 4000;
>>> +       attr.sample_type = PERF_SAMPLE_BRANCH_STACK;
>>> +       attr.branch_sample_type = PERF_SAMPLE_BRANCH_USER | PERF_SAMPLE_BRANCH_ANY;
>>> +       pfd = syscall(__NR_perf_event_open, &attr, -1, 0, -1, PERF_FLAG_FD_CLOEXEC);
>>> +       if (CHECK(pfd < 0, "perf_event_open", "err %d\n", pfd))
>>> +               goto out_destroy;
>>
>>
>> It's failing for me in kvm. Is there way to make it work?
>> CIs will be vm based too. If this test requires physical host
>> such test will keep failing in all such environments.
>> Folks will be annoyed and eventually will disable the test.
>> Can we figure out how to test in the vm from the start?
> 
> It seems there's a patchset that's adding LBR support to guest hosts:
> https://lkml.org/lkml/2019/8/6/215 . However it seems to be stuck in
> review limbo. Is there anything we can do to help that set along?
> 
> As far as hacking it, nothing really comes to mind. Seems that patchset
> is our best hope.

prog_tests/send_signal.c tests send_signal helper under nmi with 
hardware counters. It added a check to see whether the underlying
hardware counter is supported, if it is not, the test is
skipped.

Maybe we can use the same appraoch here. If perf_event_open with
PERF_TYPE_HARDWARE/PERF_SAMPLE_BRANCH_STACK failed,
we just mark the test as skipped instead of failing.

  reply	other threads:[~2020-01-26  4:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAADnVQ+Gy_Ph+83TLJkqtLM_pC2g65NhpX2vOwBH =JM3To2Thw@mail.gmail.com>
2020-01-26  4:10 ` Daniel Xu
2020-01-26  4:50   ` Yonghong Song [this message]
2020-01-26  4:52     ` Alexei Starovoitov
2020-01-26  4:59       ` Yonghong Song
2020-01-25 22:31 [PATCH v5 bpf-next 0/2] Add bpf_read_branch_records() helper Daniel Xu
2020-01-25 22:31 ` [PATCH v5 bpf-next 2/2] selftests/bpf: add bpf_read_branch_records() selftest Daniel Xu
2020-01-26  2:53   ` 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=fcbc20dd-e5ca-e779-774f-49490dc87c3b@fb.com \
    --to=yhs@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=acme@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dxu@dxuuu.xyz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=songliubraving@fb.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®