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: <alpine.DEB.2.00.0905201902060.1080@gandalf.stny.rr.com>
Date:	Wed, 20 May 2009 19:02:56 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Christoph Hellwig <hch@...radead.org>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH 1/3] tracing: add __print_flags for events


On Wed, 20 May 2009, Christoph Hellwig wrote:

> On Wed, May 20, 2009 at 06:13:37PM -0400, Steven Rostedt wrote:
> > OK, this may even save space. By passing by parameters we must load all 
> > the parameters before calling the function. Even though this is on the 
> > print side, it is still bloated. I'll convert it to an array.
> 
> Nice, thanks.
> 
> Btw, it would be nice to add a __print_symbolic cousin that looks for
> an exact match in an array.  That way we can also print translations to
> names in a way that can be read from the format file and duplicated
> by userspace apps using the binary trace buffer.

You mean more like a "__print_enumerated"? A backward translation of 
enumerated types to their names.

Perhaps __print_symbolic is a bit nicer name.

-- Steve

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ