From: Steven Rostedt <rostedt@goodmis.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: yalin wang <yalin.wang2010@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ebru Akagunduz <ebru.akagunduz@gmail.com>,
Rik van Riel <riel@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
jmarchan@redhat.com, mgorman@techsingularity.net,
willy@linux.intel.com,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH V4] mm: fix kernel crash in khugepaged thread
Date: Mon, 16 Nov 2015 09:25:01 -0500 [thread overview]
Message-ID: <20151116092501.761f31d7@gandalf.local.home> (raw)
In-Reply-To: <5649ACF6.1000704@suse.cz>
On Mon, 16 Nov 2015 11:16:22 +0100
Vlastimil Babka <vbabka@suse.cz> wrote:
>
> >> -- Steve
> > it is not easy to print for perf tools in userspace ,
> > if you use this format ,
> > for user space perf tool, it print the entry by look up the member in entry struct by offset ,
> > you print a dynamic string which user space perf tool don’t know how to print this string .
>
> Does it work through trace-cmd?
The two use the same code. If it works in one, it will work in the
other.
-- Steve
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-11-16 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 8:21 yalin wang
2015-11-12 14:29 ` Steven Rostedt
2015-11-13 10:47 ` Vlastimil Babka
2015-11-13 11:54 ` yalin wang
2015-11-13 14:01 ` Steven Rostedt
2015-11-16 1:35 ` yalin wang
2015-11-16 10:16 ` Vlastimil Babka
2015-11-16 14:25 ` Steven Rostedt [this message]
2015-11-17 2:21 ` yalin wang
2015-11-17 2:43 ` Steven Rostedt
2015-11-17 3:58 ` yalin wang
2015-11-17 7:43 ` Vlastimil Babka
2015-11-16 14:22 ` Steven Rostedt
2015-11-13 8:41 Hillf Danton
2015-11-13 10:24 ` yalin wang
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=20151116092501.761f31d7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=ebru.akagunduz@gmail.com \
--cc=jmarchan@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
--cc=willy@linux.intel.com \
--cc=yalin.wang2010@gmail.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