linux-kernel - Re: perf trace errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091011124030.GA3859@lst.de>
Date:	Sun, 11 Oct 2009 14:40:30 +0200
From:	Christoph Hellwig <hch@....de>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Christoph Hellwig <hch@....de>, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: perf trace errors

On Sun, Oct 11, 2009 at 02:19:28PM +0200, Frederic Weisbecker wrote:
> Yeah, there are still some trace events that are not well supported
> in perf trace, for now... I'll fix that by the time.

Any idea what is the missing part?  I tried to understand the code but
I haven't even managed to grasp the data structures yet.

The weird thing is that these message seem to come from parsing of
the filters, and a simple trace the whole system trace shouldn't
really have to set any filters anyway, nor should the filters depdend
on what trace point you use.

Note that the in addition to all the block trace points also all my
new xfs tracepoints also give errors from perf trace.  Things tend
to work quite nicely with the ASCII output from the kernel.

--
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/