linux-kernel - Re: [PATCHv4 0/9] perf tool: parser generator for events parsing

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: <1329303788.2293.37.camel@twins>
Date:	Wed, 15 Feb 2012 12:03:08 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	acme@...hat.com, mingo@...e.hu, paulus@...ba.org,
	cjashfor@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv4 0/9] perf tool: parser generator for events parsing

On Wed, 2012-02-15 at 10:04 +0100, Jiri Olsa wrote:
> On Tue, Feb 14, 2012 at 09:57:10PM +0100, Peter Zijlstra wrote:
> > On Tue, 2012-02-14 at 21:20 +0100, Peter Zijlstra wrote:
> > > OK, this one works. the attributes thing wants NULL termination.
> > > Thanks
> > > for mentioning that Jiri. 
> > 
> > OK, it mostly works, except:
> > 
> > perf record -e "cpu/config=0x108000c0/upp" ./loop_1b_locks
> > 
> > doesn't seem to work...
> > 
> > One thing that might be nice is not having to do =1 for single bit
> > fields, so that we can write: inv,edge instead of inv=1,edge=1.
> 
> ok, would you think there's any use for following behaviour:
> whenever field is written without the assignment, all the field defined
> bits are set.. regardless if it's sengle ot multiple bit field..
> 
> looks like this would ease the implementation a little,
> not mentioning the above behaviour could be usefull ;)

I'm not sure that behaviour would be useful for anything other than
this, but sure -- or set the value to 1 when not set, either works.
--
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/