From: Peter Zijlstra <peterz@infradead.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@fb.com>,
"David S . Miller" <davem@davemloft.net>,
Brendan Gregg <bgregg@netflix.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Wang Nan <wangnan0@huawei.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH v2 net-next 4/6] perf, bpf: add perf events core support for BPF_PROG_TYPE_PERF_EVENT programs
Date: Thu, 1 Sep 2016 18:37:22 +0200 [thread overview]
Message-ID: <20160901163722.GY10153@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160901155349.GA88787@ast-mbp.thefacebook.com>
On Thu, Sep 01, 2016 at 08:53:51AM -0700, Alexei Starovoitov wrote:
> On Thu, Sep 01, 2016 at 10:12:51AM +0200, Peter Zijlstra wrote:
> > Please, no leading space before labels. Use something like:
>
> good catch.
> sadly checkpatch didn't complain.
Right, a lot of people do it on purpose to avoid diff seeing the label
as the function for --show-c-function. I just find the style annoying
and 'fixed' diff.
Now, if the option would've been called --show-function (without the
explicit reference to C) one could argue that seeing this form is useful
for .S files but... ;-)
> > [diff "default"]
> > xfuncname = "^[[:alpha:]$_].*[^:]$"
> >
> > In your .gitconfig if you want to keep diff output 'sane'.
>
> interesting trick. don't remember being bitten by it.
> This extra space was a typo.
Example below, see the difference in the @@ line. I find the first
(fixed) to be much more useful.
With:
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 8b3ad4e26548..cc2af0188924 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -6238,6 +6238,7 @@ static void perf_pmu_output_stop(struct perf_event *event)
goto restart;
}
}
+ /* ponies */
rcu_read_unlock();
}
Without:
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 8b3ad4e26548..cc2af0188924 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -6238,6 +6238,7 @@ restart:
goto restart;
}
}
+ /* ponies */
rcu_read_unlock();
}
next prev parent reply other threads:[~2016-09-01 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 21:50 [PATCH v2 net-next 0/6] perf, bpf: add support for bpf in sw/hw perf_events Alexei Starovoitov
2016-08-31 21:50 ` [PATCH v2 net-next 1/6] bpf: support 8-byte metafield access Alexei Starovoitov
2016-08-31 21:50 ` [PATCH v2 net-next 2/6] bpf: introduce BPF_PROG_TYPE_PERF_EVENT program type Alexei Starovoitov
2016-09-01 7:44 ` Peter Zijlstra
2016-09-01 8:33 ` Daniel Borkmann
2016-08-31 21:50 ` [PATCH v2 net-next 3/6] bpf: perf_event progs should only use preallocated maps Alexei Starovoitov
2016-08-31 21:50 ` [PATCH v2 net-next 4/6] perf, bpf: add perf events core support for BPF_PROG_TYPE_PERF_EVENT programs Alexei Starovoitov
2016-09-01 8:12 ` Peter Zijlstra
2016-09-01 15:53 ` Alexei Starovoitov
2016-09-01 16:37 ` Peter Zijlstra [this message]
2016-08-31 21:50 ` [PATCH v2 net-next 5/6] samples/bpf: add perf_event+bpf example Alexei Starovoitov
2016-08-31 21:50 ` [PATCH v2 net-next 6/6] samples/bpf: add sampleip example Alexei Starovoitov
2016-09-01 0:18 ` [PATCH v2 net-next 0/6] perf, bpf: add support for bpf in sw/hw perf_events Brendan Gregg
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=20160901163722.GY10153@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=bgregg@netflix.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangnan0@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