linux-kernel - Re: [PATCH 08/12] perf: export some syscall metadata

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: <1267078193.6611.146.camel@tropicana>
Date:	Thu, 25 Feb 2010 00:09:53 -0600
From:	Tom Zanussi <tzanussi@...il.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, rostedt@...dmis.org,
	k-keiichi@...jp.nec.com
Subject: Re: [PATCH 08/12] perf: export some syscall metadata

On Thu, 2010-02-25 at 02:52 +0100, Frederic Weisbecker wrote:
> On Wed, Feb 24, 2010 at 12:00:43AM -0600, Tom Zanussi wrote:
> > You can skip the syscall metadata patches (7-11) and things will still
> > work - you'll just get syscall numbers in the output instead of the
> > nicer syscall names.
> > 
> > When the event injection stuff is ready, I can re-implement those
> > patches on top of it - it shouldn't be a big deal.
> 
> 
> Yeah, this looks more reasonable I think. The 7th patch can still
> go on though, as it deals with syscall numbers, not yet names, so
> it's fine.
> 
> Ah and I'm keeping the 12th patch too (documentation) with some
> few modifications, just to tell people syscall names are not yet
> supported.
> 
> I've tested the set and played with it. It works very well.
> 
> Actually this work is just amazing. It's so easy to generate
> a script for any perf.data, with the right things inside, easy
> to modify as the callbacks are intuitive.
> 
> I'm pushing that right away so happily...
> 

Great!  Thanks for reviewing and pushing it all.

Tom

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