From: Jiri Olsa <jolsa@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH] perf report: Fix a memory corrupton issue when enabling --branch-history
Date: Fri, 16 Feb 2018 08:53:04 +0100 [thread overview]
Message-ID: <20180216075303.GD14831@krava> (raw)
In-Reply-To: <9b3483ae-a612-9d69-9671-4ddfea2c440e@linux.intel.com>
On Fri, Feb 16, 2018 at 10:25:31AM +0800, Jin, Yao wrote:
SNIP
> > From my opinion, the option '--max-stack' in perf report looks not very
> > necessary. While it's just my personal opinion, need to hear from more
> > people. :)
> >
> > Thanks
> > Jin Yao
> >
> > > thanks,
> > > jirka
> > >
> > >
> > > ---
> > > diff --git a/tools/perf/util/hist.c b/tools/perf/util/hist.c
> > > index b6140950301e..b50b7b70dcca 100644
> > > --- a/tools/perf/util/hist.c
> > > +++ b/tools/perf/util/hist.c
> > > @@ -879,7 +879,7 @@ iter_prepare_cumulative_entry(struct
> > > hist_entry_iter *iter,
> > > * cumulated only one time to prevent entries more than 100%
> > > * overhead.
> > > */
> > > - he_cache = malloc(sizeof(*he_cache) * (iter->max_stack + 1));
> > > + he_cache = malloc(sizeof(*he_cache) * (callchain_cursor.nr + 1));
> > > if (he_cache == NULL)
> > > return -ENOMEM;
> > >
>
> Hi Jiri,
>
> I guess you will post this patch, right?
yep, later today
jirka
next prev parent reply other threads:[~2018-02-16 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 8:44 [PATCH] perf report: Fix a memory corrupton issue when enabling --branch-history Jin Yao
2018-02-13 9:45 ` Jiri Olsa
2018-02-13 14:00 ` Jin, Yao
2018-02-16 2:25 ` Jin, Yao
2018-02-16 7:53 ` Jiri Olsa [this message]
2018-02-16 12:36 ` [PATCH] perf report: Fix memory corruption in --branch-history mode --branch-history Jiri Olsa
2018-02-16 13:02 ` Arnaldo Carvalho de Melo
2018-02-17 11:34 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=20180216075303.GD14831@krava \
--to=jolsa@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--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