On Sat, Mar 29, 2014 at 06:11:38PM +0100, Jiri Olsa wrote:
> On Mon, Mar 24, 2014 at 03:36:57PM -0400, Don Zickus wrote:
> > Modified the code to allow latency settings to be tweaked on the command
> > line
> > and also the ability to dynamically profile stores (or disable using
> > stores).
> >
> > This allows the tool to be used on older Intel platforms like Westmere.
> >
> > Signed-off-by: Don Zickus <dzic...@redhat.com>
> > ---
>
> SNIP
>
> > @@ -316,6 +369,12 @@ int cmd_c2c(int argc, const char **argv, const char
> > *prefix __maybe_unused)
> > };
> > const struct option c2c_options[] = {
> > OPT_BOOLEAN('r', "raw_records", &c2c.raw_records, "dump raw events"),
> > + OPT_INTEGER('l', "latency-level", &lat_level,
> > + "specify the latency threshold for loads [default=30]"),
> > + OPT_INTEGER('p', "precision-level", &prec_level,
> > + "specify the precision level of events (0,1,2,3) [default=1]"),
>
> could we get also option for user space modifier?
You mean the 'u' modifier, ie cpu/mem-loads/u ? If so, then I can do that
but will that work with the -a option (which is hardcoded in the c2c
tool [system-wide mode])?
> I needed to hack it in for my tests ;-)
>
> thanks,
> jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
