From: Alexei Starovoitov <ast@plumgrid.com>
To: Kaixu Xia <xiakaixu@huawei.com>,
davem@davemloft.net, acme@kernel.org, mingo@redhat.com,
a.p.zijlstra@chello.nl, masami.hiramatsu.pt@hitachi.com,
jolsa@kernel.org, daniel@iogearbox.net
Cc: wangnan0@huawei.com, linux-kernel@vger.kernel.org,
pi3orama@163.com, hekuang@huawei.com, netdev@vger.kernel.org
Subject: Re: [PATCH V5 1/1] bpf: control events stored in PERF_EVENT_ARRAY maps trace data output when perf sampling
Date: Tue, 20 Oct 2015 15:53:02 -0700 [thread overview]
Message-ID: <5626C5CE.8080809@plumgrid.com> (raw)
In-Reply-To: <1445325735-121694-2-git-send-email-xiakaixu@huawei.com>
On 10/20/15 12:22 AM, Kaixu Xia wrote:
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index b11756f..5219635 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -6337,6 +6337,9 @@ static int __perf_event_overflow(struct perf_event *event,
> irq_work_queue(&event->pending);
> }
>
> + if (unlikely(!atomic_read(&event->soft_enable)))
> + return 0;
> +
> if (event->overflow_handler)
> event->overflow_handler(event, data, regs);
> else
Peter,
does this part look right or it should be moved right after
if (unlikely(!is_sampling_event(event)))
return 0;
or even to other function?
It feels to me that it should be moved, since we probably don't
want to active throttling, period adjust and event_limit for events
that are in soft_disabled state.
next prev parent reply other threads:[~2015-10-20 22:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 7:22 [PATCH V5 0/1] bpf: control events stored in PERF_EVENT_ARRAY maps trace data output when perf sampling Kaixu Xia
2015-10-20 7:22 ` [PATCH V5 1/1] " Kaixu Xia
2015-10-20 22:53 ` Alexei Starovoitov [this message]
2015-10-21 9:12 ` Peter Zijlstra
2015-10-21 10:31 ` xiakaixu
2015-10-21 11:33 ` Peter Zijlstra
2015-10-21 11:49 ` Wangnan (F)
2015-10-21 12:17 ` Peter Zijlstra
2015-10-21 13:42 ` Wangnan (F)
2015-10-21 13:49 ` Peter Zijlstra
2015-10-21 14:01 ` pi3orama
2015-10-21 14:09 ` Peter Zijlstra
2015-10-21 15:06 ` pi3orama
2015-10-21 16:57 ` Peter Zijlstra
2015-10-21 21:19 ` Alexei Starovoitov
2015-10-22 9:06 ` Peter Zijlstra
2015-10-22 10:28 ` Wangnan (F)
2015-10-23 12:52 ` Peter Zijlstra
2015-10-23 15:12 ` Peter Zijlstra
2015-10-27 6:43 ` xiakaixu
2015-10-22 2:46 ` Wangnan (F)
2015-10-22 7:39 ` Ingo Molnar
2015-10-22 7:51 ` Wangnan (F)
2015-10-22 9:24 ` Peter Zijlstra
2015-10-22 1:56 ` Wangnan (F)
2015-10-22 3:09 ` Alexei Starovoitov
2015-10-22 3:12 ` Wangnan (F)
2015-10-22 3:26 ` Alexei Starovoitov
2015-10-22 9:49 ` Peter Zijlstra
2015-10-21 11:34 ` Wangnan (F)
2015-10-21 11:56 ` Peter Zijlstra
2015-10-21 12:03 ` Wangnan (F)
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=5626C5CE.8080809@plumgrid.com \
--to=ast@plumgrid.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.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;
as well as URLs for NNTP newsgroup(s).