| 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
| ||
|
Message-ID: <20131126110536.GC3388@stfomichev-desktop> Date: Tue, 26 Nov 2013 15:05:36 +0400 From: Stanislav Fomichev <stfomichev@...dex-team.ru> To: Arnaldo Carvalho de Melo <acme@...stprotocols.net> Cc: Chia-I Wu <olvaffe@...il.com>, a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...hat.com, linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org> Subject: Re: [PATCH] perf timechart: remove lock_depth from trace_entry > This makes the new tool stop processing old files, can you try the patch > attached instead? I see two downsides to your approach: 1) with your patch I'm now required to run 'perf timechart record' and 'perf timechart' on the same machine (otherwise, on the 'perf timechart' machine we may have wrong fields definitions that don't match perf.data). Currently, it's possible to use 'perf timechart record' on the target and do 'perf timechart' on the host (at least I do it this way). 2) only root can run 'perf timechart' now (because of permissions on /sys/kernel/debug). Maybe we can we make some simple version check against the perf.data file and just refuse to process the old one (not sure if it's possible)? > Its only compile tested tho. Ok, I'll test it if we are fine with the new limitations. -- 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