From: Jiri Olsa <jolsa@redhat.com> To: Arnaldo Carvalho de Melo <acme@kernel.org> Cc: Jiri Olsa <jolsa@kernel.org>, David Ahern <dsahern@gmail.com>, Namhyung Kim <namhyung@kernel.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>, Borislav Petkov <bp@alien8.de>, lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org> Subject: Re: [PATCH 4/5] perf stat: Add -a as a default target Date: Fri, 17 Feb 2017 15:33:27 +0100 [thread overview] Message-ID: <20170217143327.GA11281@krava> (raw) In-Reply-To: <20170217142747.GD4109@kernel.org> On Fri, Feb 17, 2017 at 11:27:47AM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Feb 17, 2017 at 03:00:57PM +0100, Jiri Olsa escreveu: > > Boris asked for default -a option in case we monitor > > only uncore events. While implementing that I thought > > it might be actually useful to make it overall default. > > > > # perf stat > > Warning: No target specified, setting system-wide collection (-a). > > Humm, would be interesting to disable this after a few warnings? Just > one? not sure it's good idea to keep the count of that somewhere.. how about i make the warning smaller ;-) # perf stat Forced system wide target. ... > > BTW, this is how 'perf trace' works since day one, i.e. no target means > system wide syscall tracing. or we could omit the warning completely as probably perf trace does thanks, jirka
next prev parent reply other threads:[~2017-02-17 14:33 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-17 14:00 [PATCH 0/5] perf tools: Few fixes Jiri Olsa 2017-02-17 14:00 ` [PATCH 1/5] perf build: Add special fixdep cleaning rule Jiri Olsa 2017-02-21 8:13 ` [tip:perf/urgent] " tip-bot for Jiri Olsa 2017-02-17 14:00 ` [PATCH 2/5] perf tools: Move new_term arguments into struct parse_events_term template Jiri Olsa 2017-02-21 8:13 ` [tip:perf/urgent] " tip-bot for Jiri Olsa 2017-02-17 14:00 ` [PATCH 3/5] perf tools: Fail on using multiple bits long terms without value Jiri Olsa 2017-02-21 8:14 ` [tip:perf/urgent] " tip-bot for Jiri Olsa 2017-02-17 14:00 ` [PATCH 4/5] perf stat: Add -a as a default target Jiri Olsa 2017-02-17 14:27 ` Arnaldo Carvalho de Melo 2017-02-17 14:33 ` Jiri Olsa [this message] 2017-02-17 14:41 ` Arnaldo Carvalho de Melo 2017-02-17 14:43 ` Jiri Olsa 2017-02-17 17:00 ` [PATCHv2 " Jiri Olsa 2017-02-17 17:48 ` Boris Petkov 2017-02-18 17:52 ` Borislav Petkov 2017-02-20 7:13 ` Jiri Olsa [not found] ` <20170220134433.GI4109@kernel.org> 2017-02-20 20:31 ` Borislav Petkov 2017-02-20 21:22 ` Arnaldo Carvalho de Melo 2017-02-20 22:47 ` Borislav Petkov 2017-02-21 7:54 ` Jiri Olsa 2017-02-21 11:04 ` Jiri Olsa 2017-02-21 11:20 ` Borislav Petkov 2017-02-21 13:34 ` Arnaldo Carvalho de Melo 2017-02-21 14:05 ` Borislav Petkov 2017-02-21 14:20 ` Arnaldo Carvalho de Melo 2017-02-21 8:14 ` [tip:perf/urgent] perf stat: Add -a as " tip-bot for Jiri Olsa 2017-02-17 14:00 ` [PATCH 5/5] perf record: Add -a as a " Jiri Olsa 2017-02-17 14:28 ` Arnaldo Carvalho de Melo 2017-02-17 17:00 ` Jiri Olsa 2017-02-21 8:15 ` [tip:perf/urgent] perf record: Add -a as " tip-bot for Jiri Olsa
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20170217143327.GA11281@krava \ --to=jolsa@redhat.com \ --cc=a.p.zijlstra@chello.nl \ --cc=acme@kernel.org \ --cc=bp@alien8.de \ --cc=dsahern@gmail.com \ --cc=jolsa@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=namhyung@kernel.org \ --subject='Re: [PATCH 4/5] perf stat: Add -a as a default target' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.