From: David Miller <davem@davemloft.net>
To: xiakaixu@huawei.com
Cc: ast@plumgrid.com, acme@kernel.org, mingo@redhat.com,
a.p.zijlstra@chello.nl, masami.hiramatsu.pt@hitachi.com,
jolsa@kernel.org, daniel@iogearbox.net, wangnan0@huawei.com,
linux-kernel@vger.kernel.org, pi3orama@163.com,
hekuang@huawei.com, netdev@vger.kernel.org
Subject: Re: [PATCH v7 0/5] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter
Date: Sun, 09 Aug 2015 22:50:34 -0700 (PDT) [thread overview]
Message-ID: <20150809.225034.728930050511076416.davem@davemloft.net> (raw)
In-Reply-To: <1438844556-27064-1-git-send-email-xiakaixu@huawei.com>
From: Kaixu Xia <xiakaixu@huawei.com>
Date: Thu, 6 Aug 2015 07:02:31 +0000
> The detail of patches is as follow:
>
> Patch 1/5 add the necessary core perf APIs perf_event_attrs(),
> perf_event_get(),perf_event_read_local() when accessing events
> counters in eBPF programs
>
> Patch 2/5 rewrites part of the bpf_prog_array map code and make it
> more generic;
>
> Patch 3/5 introduces a new bpf map type. This map only stores the
> pointer to struct perf_event;
>
> Patch 4/5 implements function bpf_perf_event_read() that get the
> selected hardware PMU conuter;
>
> Patch 5/5 gives a simple example.
Series applied, thanks.
prev parent reply other threads:[~2015-08-10 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 7:02 Kaixu Xia
2015-08-06 7:02 ` [PATCH v7 1/5] perf: add the necessary core perf APIs when accessing events counters in eBPF programs Kaixu Xia
2015-08-06 7:02 ` [PATCH v7 2/5] bpf: Make the bpf_prog_array_map more generic Kaixu Xia
2015-08-06 7:02 ` [PATCH v7 3/5] bpf: Add new bpf map type to store the pointer to struct perf_event Kaixu Xia
2015-08-06 7:02 ` [PATCH v7 4/5] bpf: Implement function bpf_perf_event_read() that get the selected hardware PMU conuter Kaixu Xia
2015-08-06 7:02 ` [PATCH v7 5/5] samples/bpf: example of get selected PMU counter value Kaixu Xia
2015-08-12 1:59 ` Alexei Starovoitov
2015-08-10 5:50 ` David Miller [this message]
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=20150809.225034.728930050511076416.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.com \
--cc=xiakaixu@huawei.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
all inboxes | Powered by JetHome®