From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Qais Yousef <qais.yousef@arm.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
ast@kernel.org, atishp04@gmail.com, dancol@google.com,
Dan Williams <dan.j.williams@intel.com>,
gregkh@linuxfoundation.org, Guenter Roeck <groeck@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
karim.yaghmour@opersys.com, Kees Cook <keescook@chromium.org>,
kernel-team@android.com, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-trace-devel@vger.kernel.org,
Manoj Rao <linux@manojrajarao.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
mhiramat@kernel.org, paulmck@linux.vnet.ibm.com,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
rdunlap@infradead.org, rostedt@goodmis.org,
Shuah Khan <shuah@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
yhs@fb.com
Subject: Re: [PATCH v3 1/2] Provide in-kernel headers for making it easy to extend the kernel
Date: Thu, 28 Feb 2019 19:36:17 +0100 [thread overview]
Message-ID: <df3c8773-bda1-edcf-757b-9dc1c77cc4cf@arm.com> (raw)
In-Reply-To: <20190228164801.iahwphx5o2zeks4n@e107158-lin.cambridge.arm.com>
On 2/28/19 5:48 PM, Qais Yousef wrote:
> On 02/28/19 17:04, Dietmar Eggemann wrote:
>> Hi Joel,
>>
>> On 2/28/19 3:47 PM, Joel Fernandes wrote:
>>> On Thu, Feb 28, 2019 at 01:53:43PM +0000, Qais Yousef wrote:
>>>> Hi Joel
>>>>
>>>> On 02/27/19 14:37, Joel Fernandes (Google) wrote:
[...]
>> The reason for me to stay on v4.20 is that with v5.0-rc8 I don't have ebpf
>> 'raw tracepoint' support any more on my arm64 board. But this issue is not
>> related to your patch though.
>
> And this is caused by a38d1107f937 (bpf: support raw tracepoints in modules)
> which renamed bpf_find_raw_tracepoint() which bcc-tools relies on to detect if
> raw tracepoints are supported..
>
> https://github.com/iovisor/bcc/blob/master/src/python/bcc/__init__.py#L860
>
> Speaking of fragile depedencies :-)
>
> I guess the check can be extended to check for both symbols - but it'll stay
> fragile. Not sure if they can do better.
>
> I filed a bug
>
> https://github.com/iovisor/bcc/issues/2240
This did the trick for me on v5.0-rc8. Thanks, Qais!
next prev parent reply other threads:[~2019-02-28 18:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 19:37 [PATCH v3 1/2] Provide in-kernel headers for making it easy to extend the kernel Joel Fernandes (Google)
2019-02-27 19:37 ` [PATCH v3 2/2] Add selftests for module build using in-kernel headers Joel Fernandes (Google)
2019-02-28 2:17 ` [PATCH v3 1/2] Provide in-kernel headers for making it easy to extend the kernel Masahiro Yamada
2019-02-28 14:43 ` Joel Fernandes
2019-02-28 23:27 ` Joel Fernandes
2019-03-01 6:25 ` Masahiro Yamada
2019-03-01 17:19 ` Joel Fernandes
2019-03-02 2:13 ` Masahiro Yamada
2019-03-02 2:39 ` Joel Fernandes
2019-03-04 5:40 ` Masahiro Yamada
2019-02-28 8:34 ` Masami Hiramatsu
2019-02-28 15:00 ` Joel Fernandes
2019-02-28 15:30 ` Greg KH
2019-02-28 15:37 ` Joel Fernandes
2019-02-28 15:45 ` Greg KH
2019-02-28 15:59 ` Joel Fernandes
2019-02-28 16:09 ` Steven Rostedt
2019-03-01 2:28 ` Masami Hiramatsu
2019-03-01 3:26 ` Joel Fernandes
2019-03-01 7:03 ` Masami Hiramatsu
2019-03-01 17:21 ` Joel Fernandes
2019-03-01 11:05 ` Qais Yousef
2019-02-28 13:53 ` Qais Yousef
2019-02-28 14:47 ` Joel Fernandes
2019-02-28 16:04 ` Dietmar Eggemann
2019-02-28 16:22 ` Qais Yousef
2019-02-28 16:48 ` Qais Yousef
2019-02-28 18:36 ` Dietmar Eggemann [this message]
2019-02-28 19:10 ` Joel Fernandes
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=df3c8773-bda1-edcf-757b-9dc1c77cc4cf@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=atishp04@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dancol@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=joel@joelfernandes.org \
--cc=karim.yaghmour@opersys.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux@manojrajarao.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.com \
--cc=yhs@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;
as well as URLs for NNTP newsgroup(s).