On Fri, Sep 01, 2017 at 01:21:03AM -0700, Stephane Eranian wrote:
SNIP
> >> I am also surprised to see that perf record keep inherit=1 in
> >> system-wide mode. I don't think this
> >> is relavant in this mode. But the kernel this fails in this case,
> >> which I think is a bug. In system-wide
>
On Fri, Sep 01, 2017 at 01:21:03AM -0700, Stephane Eranian wrote:
SNIP
> >> I am also surprised to see that perf record keep inherit=1 in
> >> system-wide mode. I don't think this
> >> is relavant in this mode. But the kernel this fails in this case,
> >> which I think is a bug. In system-wide
>
On Fri, Sep 1, 2017 at 12:59 AM, Jiri Olsa wrote:
> On Wed, Aug 30, 2017 at 11:21:23PM -0700, Stephane Eranian wrote:
>> Hi,
>>
>>
>> On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
>> >> So I think we are good to go. to capture multiplexing scaling
On Fri, Sep 1, 2017 at 12:59 AM, Jiri Olsa wrote:
> On Wed, Aug 30, 2017 at 11:21:23PM -0700, Stephane Eranian wrote:
>> Hi,
>>
>>
>> On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
>> >> So I think we are good to go. to capture multiplexing scaling factor
>> >> when sampling simply use the S
On Wed, Aug 30, 2017 at 11:21:23PM -0700, Stephane Eranian wrote:
> Hi,
>
>
> On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
> >> So I think we are good to go. to capture multiplexing scaling factor
> >> when sampling simply use the S
> >> modifier.
> >> But to my
On Wed, Aug 30, 2017 at 11:21:23PM -0700, Stephane Eranian wrote:
> Hi,
>
>
> On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
> >> So I think we are good to go. to capture multiplexing scaling factor
> >> when sampling simply use the S
> >> modifier.
> >> But to my surprise, newer kernels
On Wed, Aug 30, 2017 at 11:21:23PM -0700, Stephane Eranian wrote:
SNIP
> I am also surprised to see that perf record keep inherit=1 in
> system-wide mode. I don't think this
> is relavant in this mode. But the kernel this fails in this case,
> which I think is a bug. In system-wide
> mode, the
On Wed, Aug 30, 2017 at 11:21:23PM -0700, Stephane Eranian wrote:
SNIP
> I am also surprised to see that perf record keep inherit=1 in
> system-wide mode. I don't think this
> is relavant in this mode. But the kernel this fails in this case,
> which I think is a bug. In system-wide
> mode, the
Hi,
On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
>> So I think we are good to go. to capture multiplexing scaling factor
>> when sampling simply use the S
>> modifier.
>> But to my surprise, newer kernels are not happy with the cmdline:
>> $ perf record -e cycles:S
Hi,
On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
>> So I think we are good to go. to capture multiplexing scaling factor
>> when sampling simply use the S
>> modifier.
>> But to my surprise, newer kernels are not happy with the cmdline:
>> $ perf record -e cycles:S noploop 1
>> Error:
>>
> So I think we are good to go. to capture multiplexing scaling factor
> when sampling simply use the S
> modifier.
> But to my surprise, newer kernels are not happy with the cmdline:
> $ perf record -e cycles:S noploop 1
> Error:
> The sys_perf_event_open() syscall returned with 22 (Invalid
> So I think we are good to go. to capture multiplexing scaling factor
> when sampling simply use the S
> modifier.
> But to my surprise, newer kernels are not happy with the cmdline:
> $ perf record -e cycles:S noploop 1
> Error:
> The sys_perf_event_open() syscall returned with 22 (Invalid
Hi,
On Tue, Aug 22, 2017 at 12:24 AM, Stephane Eranian wrote:
> On Tue, Aug 22, 2017 at 12:03 AM, Jiri Olsa wrote:
>>
>> On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote:
>> > On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
>> >
Hi,
On Tue, Aug 22, 2017 at 12:24 AM, Stephane Eranian wrote:
> On Tue, Aug 22, 2017 at 12:03 AM, Jiri Olsa wrote:
>>
>> On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote:
>> > On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
>> > > On Mon, Aug 21, 2017 at 4:02 PM,
On Tue, Aug 22, 2017 at 12:03 AM, Jiri Olsa wrote:
>
> On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote:
> > On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> > > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
> > > >
> > > >
On Tue, Aug 22, 2017 at 12:03 AM, Jiri Olsa wrote:
>
> On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote:
> > On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> > > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
> > > >
> > > > Stephane Eranian writes:
> > > > >
>
On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote:
> On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
> > >
> > > Stephane Eranian writes:
> > > >
> > > > To activate, the
On Mon, Aug 21, 2017 at 06:25:45PM -0700, Andi Kleen wrote:
> On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
> > >
> > > Stephane Eranian writes:
> > > >
> > > > To activate, the user must use:
> > > > $ perf record -a -R
On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
> >
> > Stephane Eranian writes:
> > >
> > > To activate, the user must use:
> > > $ perf record -a -R
> >
> > I don't know why
On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
> >
> > Stephane Eranian writes:
> > >
> > > To activate, the user must use:
> > > $ perf record -a -R
> >
> > I don't know why you're overloading the existing raw mode?
>
On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
>
> Stephane Eranian writes:
> >
> > To activate, the user must use:
> > $ perf record -a -R
>
> I don't know why you're overloading the existing raw mode?
>
> It has nothing to do with that.
>
I
On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote:
>
> Stephane Eranian writes:
> >
> > To activate, the user must use:
> > $ perf record -a -R
>
> I don't know why you're overloading the existing raw mode?
>
> It has nothing to do with that.
>
I explained this in the changelog. So that is
Stephane Eranian writes:
>
> To activate, the user must use:
> $ perf record -a -R
I don't know why you're overloading the existing raw mode?
It has nothing to do with that.
-Andi
Stephane Eranian writes:
>
> To activate, the user must use:
> $ perf record -a -R
I don't know why you're overloading the existing raw mode?
It has nothing to do with that.
-Andi
This patch allows perf record to request that event
timing be recorded in each sample. The timing consists
of time_enabled and time_running. These two values are
used to compute the multiplexing correction, i.e.,
how long an event was actually measured by the hardware.
To activate, the user must
This patch allows perf record to request that event
timing be recorded in each sample. The timing consists
of time_enabled and time_running. These two values are
used to compute the multiplexing correction, i.e.,
how long an event was actually measured by the hardware.
To activate, the user must
26 matches
Mail list logo