From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Sebastiano Miano <sebastiano.miano@polito.it>
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
mingo@redhat.com, rostedt@goodmis.org, fulvio.risso@polito.it,
brouer@redhat.com
Subject: Re: [bpf-next PATCH 2/3] bpf: add id to prog tracepoint
Date: Thu, 19 Apr 2018 11:10:53 +0200 [thread overview]
Message-ID: <20180419111053.522f41e7@redhat.com> (raw)
In-Reply-To: <152406545357.3465.11912320259045335712.stgit@localhost.localdomain>
On Wed, 18 Apr 2018 17:30:53 +0200
Sebastiano Miano <sebastiano.miano@polito.it> wrote:
> This patch adds the prog id to the bpf tracepoints
> that can be used when monitoring or inspecting prog
> related functions.
>
> Signed-off-by: Sebastiano Miano <sebastiano.miano@polito.it>
> Suggested-by: Jesper Dangaard Brouer <brouer@redhat.com>
Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-04-19 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 15:30 [bpf-next PATCH 0/3] Add ID to bpf_map/prog tracepoints Sebastiano Miano
2018-04-18 15:30 ` [bpf-next PATCH 1/3] bpf: add id to map tracepoint Sebastiano Miano
2018-04-19 9:08 ` Jesper Dangaard Brouer
2018-04-18 15:30 ` [bpf-next PATCH 2/3] bpf: add id to prog tracepoint Sebastiano Miano
2018-04-19 9:10 ` Jesper Dangaard Brouer [this message]
2018-04-18 15:30 ` [bpf-next PATCH 3/3] bpf: add sample program to trace map events Sebastiano Miano
2018-04-19 9:20 ` Jesper Dangaard Brouer
2018-04-20 0:27 ` Alexei Starovoitov
2018-04-20 9:47 ` Jesper Dangaard Brouer
2018-04-23 14:08 ` Sebastiano Miano
2018-04-23 20:08 ` Alexei Starovoitov
2018-04-23 20:22 ` Jesper Dangaard Brouer
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=20180419111053.522f41e7@redhat.com \
--to=brouer@redhat.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=fulvio.risso@polito.it \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sebastiano.miano@polito.it \
/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).