[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <233209B0-A466-4149-93C6-7173FF0FD4C5@gmail.com>
Date: Tue, 17 Nov 2015 10:21:47 +0800
From: yalin wang <yalin.wang2010@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Vlastimil Babka <vbabka@...e.cz>, Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ebru Akagunduz <ebru.akagunduz@...il.com>,
Rik van Riel <riel@...hat.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
jmarchan@...hat.com, mgorman@...hsingularity.net,
willy@...ux.intel.com, linux-kernel <linux-kernel@...r.kernel.org>,
linux-mm@...ck.org
Subject: Re: [PATCH V4] mm: fix kernel crash in khugepaged thread
> On Nov 16, 2015, at 22:25, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Mon, 16 Nov 2015 11:16:22 +0100
> Vlastimil Babka <vbabka@...e.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
>
i have not tried ,
just a question,
if you print a %s , but don’t call trace_define_field() do define this string in
__entry , how does user space perf tool to get this string info and print it ?
i am curious ..
i can try this when i have time. and report to you .
Thanks--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists