ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Josef Bacik <jbacik@fb.com>,
	"ksummit-discuss@lists.linux-foundation.org"
	<ksummit-discuss@lists.linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Josef Bacik <josef@toxicpanda.com>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] tracepoints without user space interfaces
Date: Thu, 21 Sep 2017 18:45:24 +0900	[thread overview]
Message-ID: <20170921094524.GF773@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170920111306.1a74f2ec@gandalf.local.home>

Hello,

On (09/20/17 11:13), Steven Rostedt wrote:
> On Wed, 20 Sep 2017 11:04:05 -0400
> Josef Bacik <josef@toxicpanda.com> wrote:
> 
> > The tricky part is we want to be able to access these from eBPF.  I argue that
> > eBPF is run in the kernel so it has the same rules as kernel modules.  Others
> > seem less convinced of this argument, so it would be good to get a definitive
> > answer.  Thanks,
> 
> Note, adding a module to let eBPF access these tracepoints would also
> be trivial. Would a module be of issue at FB? It could be easily added
> at boot up.

JFI, seems that Josef's reply didn't make it to the ksummit-discuss list.
I'm interested in this topic, tho.

	-ss

  reply	other threads:[~2017-09-21  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 13:50 Steven Rostedt
2017-09-20 14:54 ` Josef Bacik
2017-09-20 15:04   ` Josef Bacik
2017-09-20 15:13     ` Steven Rostedt
2017-09-21  9:45       ` Sergey Senozhatsky [this message]
2017-09-29 23:50     ` Alexei Starovoitov
2017-10-04  0:55       ` Steven Rostedt

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=20170921094524.GF773@jagdpanzerIV.localdomain \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=jbacik@fb.com \
    --cc=josef@toxicpanda.com \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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