From: Jiri Olsa <jolsa@redhat.com>
To: Wang Nan <wangnan0@huawei.com>
Cc: linux-kernel@vger.kernel.org, kan.liang@intel.com,
acme@kernel.org, namhyung@kernel.org
Subject: Re: [PATCH 7/7] perf tools: Remove prot field in mmap param
Date: Mon, 13 Nov 2017 12:52:16 +0100 [thread overview]
Message-ID: <20171113115216.GA3017@krava> (raw)
In-Reply-To: <20171113013809.212417-8-wangnan0@huawei.com>
On Mon, Nov 13, 2017 at 01:38:09AM +0000, Wang Nan wrote:
> After removing the concept of 'overwrite' in code level, now the
> prot is determinated by write_backward. There's no need to pass
> prot from perf_evlist__mmap_ex().
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> ---
> tools/perf/util/evlist.c | 17 ++++++-----------
> tools/perf/util/mmap.c | 4 ++--
> tools/perf/util/mmap.h | 4 ++--
> 3 files changed, 10 insertions(+), 15 deletions(-)
>
> diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> index 4948d3d..0d713e0 100644
> --- a/tools/perf/util/evlist.c
> +++ b/tools/perf/util/evlist.c
> @@ -799,28 +799,23 @@ perf_evlist__should_poll(struct perf_evlist *evlist __maybe_unused,
> }
>
> static int perf_evlist__mmap_per_evsel(struct perf_evlist *evlist, int idx,
> - struct mmap_params *_mp, int cpu_idx,
> + struct mmap_params *mp, int cpu_idx,
> int thread, int *_output, int *_output_backward)
> {
> struct perf_evsel *evsel;
> int revent;
> int evlist_cpu = cpu_map__cpu(evlist->cpus, cpu_idx);
> - struct mmap_params *mp;
>
> evlist__for_each_entry(evlist, evsel) {
> struct perf_mmap *maps = evlist->mmap;
> - struct mmap_params rdonly_mp;
> int *output = _output;
> int fd;
> int cpu;
> + int prot = PROT_READ;
can't you set the PROT_READ in struct mmap_params *mp as its default value?
mp->prot = PROT_READ;
>
> - mp = _mp;
> if (evsel->attr.write_backward) {
> output = _output_backward;
> maps = evlist->backward_mmap;
> - rdonly_mp = *_mp;
> - rdonly_mp.prot &= ~PROT_WRITE;
> - mp = &rdonly_mp;
>
> if (!maps) {
> maps = perf_evlist__alloc_mmap(evlist);
> @@ -830,6 +825,8 @@ static int perf_evlist__mmap_per_evsel(struct perf_evlist *evlist, int idx,
> if (evlist->bkw_mmap_state == BKW_MMAP_NOTREADY)
> perf_evlist__toggle_bkw_mmap(evlist, BKW_MMAP_RUNNING);
> }
> + } else {
> + prot |= PROT_WRITE;
> }
>
> if (evsel->system_wide && thread)
> @@ -844,7 +841,7 @@ static int perf_evlist__mmap_per_evsel(struct perf_evlist *evlist, int idx,
> if (*output == -1) {
> *output = fd;
>
> - if (perf_mmap__mmap(&maps[idx], mp, *output) < 0)
> + if (perf_mmap__mmap(&maps[idx], mp, prot, *output) < 0)
so there's no need for the extra 'prot' param in here
jirka
next prev parent reply other threads:[~2017-11-13 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 1:38 [PATCH 0/7] perf tools: Clarify overwrite and backward, bugfix Wang Nan
2017-11-13 1:38 ` [PATCH 1/7] perf mmap: Fix perf backward recording Wang Nan
2017-11-13 1:38 ` [PATCH 2/7] perf tests: Set evlist of test__backward_ring_buffer() to !overwrite Wang Nan
2017-11-13 18:30 ` Arnaldo Carvalho de Melo
2017-11-18 8:30 ` [tip:perf/core] " tip-bot for Wang Nan
2017-11-13 1:38 ` [PATCH 3/7] perf tests: Set evlist of test__sw_clock_freq() " Wang Nan
2017-11-13 18:31 ` Arnaldo Carvalho de Melo
2017-11-18 8:30 ` [tip:perf/core] " tip-bot for Wang Nan
2017-11-13 1:38 ` [PATCH 4/7] perf tests: Set evlist of test__basic_mmap() " Wang Nan
2017-11-13 18:31 ` Arnaldo Carvalho de Melo
2017-11-18 8:31 ` [tip:perf/core] " tip-bot for Wang Nan
2017-11-13 1:38 ` [PATCH 5/7] perf tests: Set evlist of test__task_exit() " Wang Nan
2017-11-13 18:32 ` Arnaldo Carvalho de Melo
2017-11-18 8:31 ` [tip:perf/core] " tip-bot for Wang Nan
2017-11-13 1:38 ` [PATCH 6/7] perf tools: Remove 'overwrite' concept from code level Wang Nan
2017-11-13 11:52 ` Jiri Olsa
2017-11-13 15:07 ` Liang, Kan
2017-11-13 1:38 ` [PATCH 7/7] perf tools: Remove prot field in mmap param Wang Nan
2017-11-13 11:52 ` Jiri Olsa [this message]
2017-11-13 11:52 ` Jiri Olsa
2017-11-13 14:49 ` [PATCH 0/7] perf tools: Clarify overwrite and backward, bugfix Liang, Kan
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=20171113115216.GA3017@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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