From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Valentin Schneider" <valentin.schneider@arm.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Jirka Hladký" <jhladky@redhat.com>,
"Jiří Vozár" <jvozar@redhat.com>, "X86 ML" <x86@kernel.org>,
"Qais Yousef" <qais.yousef@arm.com>
Subject: Re: [PATCH 2/2] sched/debug: add sched_update_nr_running tracepoint
Date: Wed, 4 Sep 2019 08:26:52 -0700 [thread overview]
Message-ID: <CAADnVQL3CsB6z98BFWd8wn7WKk+W4UVH2NbzrhJgeaU-D-n3ug@mail.gmail.com> (raw)
In-Reply-To: <20190904131154.GF144846@google.com>
On Wed, Sep 4, 2019 at 6:14 AM Joel Fernandes <joel@joelfernandes.org> wrote:
>
> True. However, for kprobes-based BPF program - it does check for kernel
> version to ensure that the BPF program is built against the right kernel
> version (in order to ensure the program is built against the right set of
> kernel headers). If it is not, then BPF refuses to load the program.
This is not true anymore. Users found few ways to workaround that check
in practice. It became useless and it was deleted some time ago.
next prev parent reply other threads:[~2019-09-04 15:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 15:43 [PATCH 0/2] sched/debug: add sched_update_nr_running tracepoint Radim Krčmář
2019-09-03 15:43 ` [PATCH 1/2] x86/mm/tlb: include tracepoints from tlb.c instead of mmu_context.h Radim Krčmář
2019-09-03 15:43 ` [PATCH 2/2] sched/debug: add sched_update_nr_running tracepoint Radim Krčmář
2019-09-03 16:05 ` Valentin Schneider
2019-09-04 4:23 ` Joel Fernandes
2019-09-04 8:14 ` Peter Zijlstra
2019-09-04 10:52 ` Qais Yousef
2019-09-04 13:11 ` Joel Fernandes
2019-09-04 15:26 ` Alexei Starovoitov [this message]
2019-09-04 15:33 ` Joel Fernandes
2019-09-04 15:37 ` Alexei Starovoitov
2019-09-04 15:41 ` Joel Fernandes
2019-09-04 10:43 ` Qais Yousef
2019-09-04 13:06 ` Joel Fernandes
2019-09-04 14:20 ` Qais Yousef
2019-09-04 14:41 ` Joel Fernandes
2019-09-04 14:57 ` Qais Yousef
2019-09-04 15:46 ` Joel Fernandes
2019-09-04 15:25 ` Alexei Starovoitov
2019-09-04 15:40 ` Joel Fernandes
2019-09-04 15:51 ` Alexei Starovoitov
2019-09-04 17:47 ` Peter Zijlstra
2019-09-04 17:53 ` Alexei Starovoitov
2019-09-05 8:13 ` Ingo Molnar
2019-09-05 16:49 ` Alexei Starovoitov
2019-09-04 6:55 ` chengjian (D)
2019-09-04 13:13 ` Peter Zijlstra
2019-09-04 13:21 ` Valentin Schneider
2019-09-04 14:37 ` Qais Yousef
2019-09-04 17:48 ` Peter Zijlstra
2019-09-09 10:59 ` Qais Yousef
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=CAADnVQL3CsB6z98BFWd8wn7WKk+W4UVH2NbzrhJgeaU-D-n3ug@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jhladky@redhat.com \
--cc=joel@joelfernandes.org \
--cc=jvozar@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=rkrcmar@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
--cc=x86@kernel.org \
/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).