On Tue, Nov 05, 2013 at 03:09:30PM +0200, Adrian Hunter wrote: SNIP
> >> Another advantage of per-thread mmaps is that you do not > >> need to sample time (nor cpu), because the events are recorded > >> in order. > >> > >> I was adding a feature. Users can choose per-cpu mmaps if > >> they want. > > > > right, I haven't considered the hundreds CPU machine.. I just > > saw that it disables inherited events in my test ;-) maybe we > > could mentioned that somewhere, because it's not clear > > How about this: > > From: Adrian Hunter <[email protected]> > > By default, when tasks are specified (i.e. -p, -t > or -u options) per-thread mmaps are created. Add > an option to override that and force per-cpu mmaps. > > Signed-off-by: Adrian Hunter <[email protected]> seems ok, thanks Acked-by: Jiri Olsa <[email protected]> jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
