On Fri, 1 Sep 2017 10:16:21 +0200
Vlastimil Babka wrote:
> > Right, but that should work with the latest trace-cmd. Does it?
>
> Hmm, by "sparse memory model without vmemmap" I don't mean there's a
> number instead of "vmemmap_base". I mean CONFIG_SPARSEMEM=y
>
> Then __pfn_to_page() looks l
On 08/31/2017 04:44 PM, Steven Rostedt wrote:
> On Thu, 31 Aug 2017 16:31:36 +0200
> Vlastimil Babka wrote:
>
>
>>> Which version of trace-cmd failed? It parses for me. Hmm, the
>>> vmemmap_base isn't in the event format file. It's the actually address.
>>> That's probably what failed to parse.
On Thu, 31 Aug 2017 16:31:36 +0200
Vlastimil Babka wrote:
> > Which version of trace-cmd failed? It parses for me. Hmm, the
> > vmemmap_base isn't in the event format file. It's the actually address.
> > That's probably what failed to parse.
>
> Mine says 2.6. With 4.13-rc6 I get FAILED TO PA
On 08/31/2017 03:43 PM, Steven Rostedt wrote:
> On Mon, 31 Jul 2017 09:43:41 +0200 Vlastimil Babka wrote:
>
>> On 04/14/2015 12:14 AM, Arnaldo Carvalho de Melo wrote:
>>> From: Namhyung Kim
>>>
>>> The struct page is opaque for userspace tools, so it'd be better to save
>>> pfn in order to ident
On Mon, 31 Jul 2017 09:43:41 +0200 Vlastimil Babka wrote:
> On 04/14/2015 12:14 AM, Arnaldo Carvalho de Melo wrote:
> > From: Namhyung Kim
> >
> > The struct page is opaque for userspace tools, so it'd be better to save
> > pfn in order to identify page frames.
> >
> > The textual output of $d
Ping?
On 07/31/2017 09:43 AM, Vlastimil Babka wrote:
> On 04/14/2015 12:14 AM, Arnaldo Carvalho de Melo wrote:
>> From: Namhyung Kim
>>
>> The struct page is opaque for userspace tools, so it'd be better to save
>> pfn in order to identify page frames.
>>
>> The textual output of $debugfs/tracing
On 04/14/2015 12:14 AM, Arnaldo Carvalho de Melo wrote:
> From: Namhyung Kim
>
> The struct page is opaque for userspace tools, so it'd be better to save
> pfn in order to identify page frames.
>
> The textual output of $debugfs/tracing/trace file remains unchanged and
> only raw (binary) data f
From: Namhyung Kim
The struct page is opaque for userspace tools, so it'd be better to save
pfn in order to identify page frames.
The textual output of $debugfs/tracing/trace file remains unchanged and
only raw (binary) data format is changed - but thanks to libtraceevent,
userspace tools which
8 matches
Mail list logo