From: Andi Kleen <ak@linux.intel.com>
To: Josh Hunt <johunt@akamai.com>
Cc: mingo@redhat.com, acme@kernel.org, peterz@infradead.org,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, wangnan0@huawei.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, kirill.shutemov@linux.intel.com
Subject: Re: [PATCH v2] perf tools: allow map files to specify DSO
Date: Mon, 7 May 2018 17:34:16 -0700 [thread overview]
Message-ID: <20180508003416.GG4050@tassilo.jf.intel.com> (raw)
In-Reply-To: <e6272e7c-25fd-0d2d-4199-fcf3ec604546@akamai.com>
On Mon, May 07, 2018 at 02:30:32PM -0700, Josh Hunt wrote:
> On 05/07/2018 11:40 AM, Andi Kleen wrote:
> > On Mon, May 07, 2018 at 02:24:16PM -0400, Josh Hunt wrote:
> > > Add the ability to specify a DSO in the /tmp/perf-<PID>.map file.
> > > The DSO should be the first line in the file and readable by the
> > > running user. If a valid DSO is found all other contents of the
> > > file will be ignored. This allows things like callchain unwinding
> > > with DWARF to work.
> >
> > FWIW it's ok, but also obsolete with Kirill's large-pages-in-tmpfs
> > work in newer kernels. With that you can just copy the executable into
> > a 2MB tmpfs and disable the manual huge page copying and everything
> > should work as usually.
> >
> > So essentially it's only a hack for old kernels and old binaries.
> >
> > But doesn't hurt I guess.
>
> Ah, very interesting. I wasn't aware of this. Can you point me to some more
> details on this process?
See commit 5a6e75f8110c97e2a5488894d4e922187e6cb343
-Andi
prev parent reply other threads:[~2018-05-08 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 18:24 Josh Hunt
2018-05-07 18:40 ` Andi Kleen
2018-05-07 21:30 ` Josh Hunt
2018-05-08 0:34 ` Andi Kleen [this message]
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=20180508003416.GG4050@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=johunt@akamai.com \
--cc=jolsa@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome