All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: Song Liu <songliubraving@fb.com>,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	kbuild-all@lists.01.org, acme@kernel.org, mingo@redhat.com,
	kjain@linux.ibm.com, kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 2/3] bpf: introduce helper bpf_get_branch_snapshot
Date: Mon, 30 Aug 2021 12:47:40 +0200	[thread overview]
Message-ID: <20210830104740.GK4353@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <202108272326.sMsn5b1g-lkp@intel.com>

On Fri, Aug 27, 2021 at 11:10:39PM +0800, kernel test robot wrote:

> All errors (new ones prefixed by >>):
> 
>    riscv32-linux-ld: kernel/bpf/trampoline.o: in function `.L57':
> >> trampoline.c:(.text+0x34c): undefined reference to `__SCK__perf_snapshot_branch_stack'
>    riscv32-linux-ld: kernel/bpf/trampoline.o: in function `.L61':
>    trampoline.c:(.text+0x360): undefined reference to `bpf_perf_branch_snapshot'
> 

This a build with PERF_EVENTS=n, I suppose you'd better make calling
perf_snapshot_branch_stack() dependent on having that :-)

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 bpf-next 2/3] bpf: introduce helper bpf_get_branch_snapshot
Date: Mon, 30 Aug 2021 12:47:40 +0200	[thread overview]
Message-ID: <20210830104740.GK4353@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <202108272326.sMsn5b1g-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

On Fri, Aug 27, 2021 at 11:10:39PM +0800, kernel test robot wrote:

> All errors (new ones prefixed by >>):
> 
>    riscv32-linux-ld: kernel/bpf/trampoline.o: in function `.L57':
> >> trampoline.c:(.text+0x34c): undefined reference to `__SCK__perf_snapshot_branch_stack'
>    riscv32-linux-ld: kernel/bpf/trampoline.o: in function `.L61':
>    trampoline.c:(.text+0x360): undefined reference to `bpf_perf_branch_snapshot'
> 

This a build with PERF_EVENTS=n, I suppose you'd better make calling
perf_snapshot_branch_stack() dependent on having that :-)

  reply	other threads:[~2021-08-30 10:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 22:13 [PATCH v2 bpf-next 0/3] bpf: introduce bpf_get_branch_snapshot Song Liu
2021-08-26 22:13 ` [PATCH v2 bpf-next 1/3] perf: enable branch record for software events Song Liu
2021-08-30 10:22   ` Peter Zijlstra
2021-08-30 15:25     ` Song Liu
2021-08-30 16:06       ` Peter Zijlstra
2021-08-30 16:36         ` Song Liu
2021-09-01 17:09           ` Peter Zijlstra
2021-08-30 17:41     ` Song Liu
2021-08-30 18:07       ` Peter Zijlstra
2021-09-01 17:12         ` Peter Zijlstra
2021-09-04 23:01           ` Josh Poimboeuf
2021-08-30 10:43   ` Peter Zijlstra
2021-08-30 16:06     ` Song Liu
2021-08-26 22:13 ` [PATCH v2 bpf-next 2/3] bpf: introduce helper bpf_get_branch_snapshot Song Liu
2021-08-27  9:28   ` kernel test robot
2021-08-27  9:28     ` kernel test robot
2021-08-27 15:10   ` kernel test robot
2021-08-27 15:10     ` kernel test robot
2021-08-30 10:47     ` Peter Zijlstra [this message]
2021-08-30 10:47       ` Peter Zijlstra
2021-08-26 22:13 ` [PATCH v2 bpf-next 3/3] selftests/bpf: add test for bpf_get_branch_snapshot Song Liu

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=20210830104740.GK4353@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=kernel-team@fb.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@redhat.com \
    --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 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.