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: Mon, 16 Apr 2018 12:30:17 +0200 From: Jiri Olsa <jolsa@...hat.com> To: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com> Cc: Masami Hiramatsu <mhiramat@...nel.org>, acme@...hat.com, kstewart@...uxfoundation.org, tglx@...utronix.de, pombredanne@...b.com, linux-kernel@...r.kernel.org, peterz@...radead.org, mingo@...hat.com, alexander.shishkin@...ux.intel.com, namhyung@...nel.org, uneedsihyeon@...il.com, kjlx@...pleofstupid.com, ravi Bangoria <ravi.bangoria@...ux.ibm.com> Subject: Re: [PATCH 3/3] perf/buildid-cache: Support --purge-all option On Mon, Apr 16, 2018 at 03:10:40PM +0530, Ravi Bangoria wrote: > Hi Masami, > > On 04/16/2018 02:57 PM, Masami Hiramatsu wrote: > > On Mon, 9 Apr 2018 16:36:33 +0530 > > Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com> wrote: > > > >> User can remove files from cache using --remove/--purge options > >> but both needs list of files as an argument. It's not convenient > >> when you want to flush out entire cache. Add an option to purge > >> all files from cache. > >> > >> Ex, > >> # perf buildid-cache -l > >> /tmp/a.out (8a86ef73e44067bca52cc3f6cd3e5446c783391c) > >> /tmp/a.out.1 (ebe71fdcf4b366518cc154d570a33cd461a51c36) > >> # perf buildid-cache -P -v > >> Removing /tmp/a.out (8a86ef73e44067bca52cc3f6cd3e5446c783391c): Ok > >> Removing /tmp/a.out.1 (ebe71fdcf4b366518cc154d570a33cd461a51c36): Ok > >> Purged all: Ok > > Hmm, for purging all caches will be done by > > > > $ rm -rf ~/.debug > > > > Are there any difference? > > No logical difference if you know it's ~/.debug where it goes. :) > I also used to do rm -rf earlier. > > This option is for a perf users. But I'm fine if it's not really needed. > Will drop it. I'd keep it.. as you said it could be configured at some other dir jirka
Powered by blists - more mailing lists