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
| ||
|
Date: Tue, 25 Jun 2013 11:37:06 +0200 From: Borislav Petkov <bp@...en8.de> To: Robert Richter <rric@...nel.org> Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>, Arnaldo Carvalho de Melo <acme@...radead.org>, Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org, Borislav Petkov <bp@...e.de> Subject: Re: [PATCH v2 03/14] perf: Add persistent event facilities On Tue, Jun 25, 2013 at 11:24:39AM +0200, Robert Richter wrote: > On 25.06.13 09:44:01, Peter Zijlstra wrote: > > Elsewhere in this series you use 'pers' to shorten things; it reads a > > bit odd to me because 'pers' is the Dutch word for press (both meanings > > transfer) but that is just something I'll have to live with isn't it ;-) > > > > As for tracepoint, it seems common to shorten that to tp; which always > > reminds me of toilet paper, but I suppose more people suffer from that. > > > > Yielding: perf_add_pers_tp() > > > > which I read as adding pressed toilet paper.. a well :-) > > Better we avoid this, don't wonat you misread the code. ;) > > I also see 'pers_' not as an optimum since it could be mixed-up easily > with 'perf_'. Maybe we take 'persist_' instead? Yep, although it reads wrong: perf_add_persist_event Another not really optimal idea would be to call them sticky events: perf_add_sticky_event. Also funny. Then there's perf_add_prstnt_event Also, not really great. Hmmm.. I got nothing so far... -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- 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