From: "Wangnan (F)" <wangnan0@huawei.com>
To: <kan.liang@intel.com>, <acme@kernel.org>, <peterz@infradead.org>,
<mingo@redhat.com>, <linux-kernel@vger.kernel.org>
Cc: <jolsa@kernel.org>, <namhyung@kernel.org>, <ak@linux.intel.com>,
<yao.jin@linux.intel.com>
Subject: Re: [PATCH V2 1/8] perf tools: remove stale perf evlist mmap read for backward
Date: Mon, 18 Dec 2017 14:44:43 +0800 [thread overview]
Message-ID: <3fc4a685-92de-bdc1-a3c5-11d44a95f600@huawei.com> (raw)
In-Reply-To: <1512603183-42754-2-git-send-email-kan.liang@intel.com>
On 2017/12/7 7:32, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
>
> perf_evlist__mmap_read_catchup and perf_evlist__mmap_read_backward are
> only for overwrite mode.
> But they read the evlist->mmap buffer which is for non-overwrite mode.
>
> It did not bring any serious problem yet, because there is no one use
> it.
>
> Remove the unused interfaces.
>
> Signed-off-by: Kan Liang <kan.liang@intel.com>
Acked-by: Wang Nan <wangnan0@huawei.com>
> ---
> tools/perf/util/evlist.c | 17 -----------------
> tools/perf/util/evlist.h | 4 ----
> 2 files changed, 21 deletions(-)
>
> diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> index 3570355..4b6a06d 100644
> --- a/tools/perf/util/evlist.c
> +++ b/tools/perf/util/evlist.c
> @@ -714,28 +714,11 @@ union perf_event *perf_evlist__mmap_read_forward(struct perf_evlist *evlist, int
> return perf_mmap__read_forward(md);
> }
>
> -union perf_event *perf_evlist__mmap_read_backward(struct perf_evlist *evlist, int idx)
> -{
> - struct perf_mmap *md = &evlist->mmap[idx];
> -
> - /*
> - * No need to check messup for backward ring buffer:
> - * We can always read arbitrary long data from a backward
> - * ring buffer unless we forget to pause it before reading.
> - */
> - return perf_mmap__read_backward(md);
> -}
> -
> union perf_event *perf_evlist__mmap_read(struct perf_evlist *evlist, int idx)
> {
> return perf_evlist__mmap_read_forward(evlist, idx);
> }
>
> -void perf_evlist__mmap_read_catchup(struct perf_evlist *evlist, int idx)
> -{
> - perf_mmap__read_catchup(&evlist->mmap[idx]);
> -}
> -
> void perf_evlist__mmap_consume(struct perf_evlist *evlist, int idx)
> {
> perf_mmap__consume(&evlist->mmap[idx], false);
> diff --git a/tools/perf/util/evlist.h b/tools/perf/util/evlist.h
> index 7516066..a80fd47 100644
> --- a/tools/perf/util/evlist.h
> +++ b/tools/perf/util/evlist.h
> @@ -132,10 +132,6 @@ union perf_event *perf_evlist__mmap_read(struct perf_evlist *evlist, int idx);
>
> union perf_event *perf_evlist__mmap_read_forward(struct perf_evlist *evlist,
> int idx);
> -union perf_event *perf_evlist__mmap_read_backward(struct perf_evlist *evlist,
> - int idx);
> -void perf_evlist__mmap_read_catchup(struct perf_evlist *evlist, int idx);
> -
> void perf_evlist__mmap_consume(struct perf_evlist *evlist, int idx);
>
> int perf_evlist__open(struct perf_evlist *evlist);
next prev parent reply other threads:[~2017-12-18 6:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 23:32 [PATCH V2 0/8] perf top overwrite mode kan.liang
2017-12-06 23:32 ` [PATCH V2 1/8] perf tools: remove stale perf evlist mmap read for backward kan.liang
2017-12-18 6:44 ` Wangnan (F) [this message]
2017-12-06 23:32 ` [PATCH V2 2/8] perf tools: rewrite perf mmap read for overwrite kan.liang
2017-12-18 8:49 ` Wangnan (F)
2017-12-18 19:07 ` Liang, Kan
2017-12-19 3:04 ` Wangnan (F)
2017-12-19 15:23 ` Liang, Kan
2017-12-06 23:32 ` [PATCH V2 3/8] perf tools: reuse perf_mmap__read_catchup in perf_mmap__push kan.liang
2017-12-06 23:32 ` [PATCH V2 4/8] perf tools: introduce perf_mmap__read_event kan.liang
2017-12-06 23:33 ` [PATCH V2 5/8] perf top: check per event overwrite term kan.liang
2017-12-06 23:33 ` [PATCH V2 6/8] perf top: add overwrite fall back kan.liang
2017-12-18 9:23 ` Wangnan (F)
2017-12-18 19:13 ` Liang, Kan
2017-12-06 23:33 ` [PATCH V2 7/8] perf top: switch default mode to overwrite mode kan.liang
2017-12-06 23:33 ` [PATCH V2 8/8] perf top: check the latency of perf_top__mmap_read kan.liang
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=3fc4a685-92de-bdc1-a3c5-11d44a95f600@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.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®