From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "Wangnan (F)" <wangnan0@huawei.com>,
acme@kernel.org, kan.liang@intel.com,
linux-kernel@vger.kernel.org, lizefan@huawei.com,
pi3orama@163.com, Adrian Hunter <adrian.hunter@intel.com>,
Andi Kleen <ak@linux.intel.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf report: Fix invalid memory accessing
Date: Tue, 8 Sep 2015 17:34:56 +0200 [thread overview]
Message-ID: <20150908153456.GG2038@krava.brq.redhat.com> (raw)
In-Reply-To: <20150908151813.GF2435@redhat.com>
On Tue, Sep 08, 2015 at 12:18:13PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 08, 2015 at 09:37:47AM +0200, Jiri Olsa escreveu:
> > On Mon, Sep 07, 2015 at 09:27:26PM +0800, Wangnan (F) wrote:
> >
> > SNIP
> >
> > >
> > > I found the problem.
> > >
> > > perf relies on build_cpu_topology() to fetch CPU_TOPOLOGY from sysfs. It
> > > depend on
> > > the existance of
> > >
> > > /sys/devices/system/cpu/cpu%d/topology/core_siblings_list
> > >
> > > However, CPU can be canceled by hotcpu subsystem. After that the directory
> > > of
> > > /sys/devices/system/cpu/cpu%d/topology is gone, which causes perf's
> > > write_cpu_topology() --> uild_cpu_topology() to fail, result in the above
> > > perf.data.
> > >
> > > So I think my patch is required.
> >
> > no question there.. I just meant it should be placed in
> > perf_event__preprocess_sample function with the rest of
> > the 'al' initialization, like in the patch below?
> >
> > it does not compile, because there're many places calling
> > it and it'd need changing all callers to pass env, which
> > seems to require more changes..
>
> Humm, I think that we can have a pointer to the current perf_env, be it
> from the current machine, or from the machine environment in the
> perf.data file in struct machine, that way we don't need to change that
> function prototype, I'm prototyping this now, will post a patch.
I was thinking of that.. but the perf_env is actualyl related to the
perf.data not to the current machine.. I think it should be part of
the session or perf_header
jirka
next prev parent reply other threads:[~2015-09-08 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:51 [PATCH] perf report: Fix invalid memory accessing Wang Nan
2015-09-07 13:03 ` Jiri Olsa
2015-09-07 13:08 ` Wangnan (F)
2015-09-07 13:27 ` Wangnan (F)
2015-09-08 7:37 ` Jiri Olsa
2015-09-08 8:12 ` Wangnan (F)
2015-09-08 13:13 ` Jiri Olsa
2015-09-08 13:16 ` pi3orama
2015-09-08 13:33 ` Jiri Olsa
2015-09-08 13:42 ` Liang, Kan
2015-09-08 15:18 ` Arnaldo Carvalho de Melo
2015-09-08 15:34 ` Jiri Olsa [this message]
[not found] ` <20150908154910.GN3475@kernel.org>
2015-09-08 15:58 ` Arnaldo Carvalho de Melo
2015-09-08 16:13 ` Arnaldo Carvalho de Melo
2015-09-08 16:35 ` Arnaldo Carvalho de Melo
2015-09-09 16:06 ` Arnaldo Carvalho de Melo
2015-09-09 16:46 ` Arnaldo Carvalho de Melo
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=20150908153456.GG2038@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=namhyung@kernel.org \
--cc=pi3orama@163.com \
--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