From: Andi Kleen <andi@firstfloor.org>
To: "Zhu, Wen-Jie (Joshua)" <zhu.wen-jie@hp.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: perf-<pid>.map I generated for jit codes lose effect when hugepage used
Date: Mon, 31 Dec 2012 11:40:57 -0800 [thread overview]
Message-ID: <m2bodac8mu.fsf@firstfloor.org> (raw)
In-Reply-To: <C9CE69BB2598EB41AAEEDA105E742F4884B55FF1@G9W0727.americas.hpqcorp.net> (Wen-Jie Zhu's message of "Mon, 31 Dec 2012 06:02:27 +0000")
"Zhu, Wen-Jie (Joshua)" <zhu.wen-jie@hp.com> writes:
>
> Therefore in order to avoid this problem, I temporarily change the codes of is_anon_memory() into following:
> return (strcmp(filename, "//anon") && strcmp(filename, "/anon_hugepage (deleted)")) == 0;
>
> I already verify this problem in kernel 3.5.0-21-generic and RHEL kernel 2.6.32-279.el6.
>
> Do you have any better solution replacement?
Your fix looks good to me, probably you just need to send it as a more
formal patch.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2012-12-31 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 6:02 perf-<pid>.map I generated for jit codes lose effect when hugepage used Zhu, Wen-Jie (Joshua)
2012-12-31 19:40 ` 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=m2bodac8mu.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=zhu.wen-jie@hp.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;
as well as URLs for NNTP newsgroup(s).