On Mon, Oct 09, 2017 at 04:00:00PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon escreveu:
> > On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> > > Currently, perf record is broken on arm/arm64 systems when the PMU is
> > > specified
On Mon, Oct 09, 2017 at 04:00:00PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon escreveu:
> > On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> > > Currently, perf record is broken on arm/arm64 systems when the PMU is
> > > specified
Em Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon escreveu:
> On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> > Currently, perf record is broken on arm/arm64 systems when the PMU is
> > specified explicitly as part of the event, e.g.
> >
> > $ ./perf record -e
Em Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon escreveu:
> On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> > Currently, perf record is broken on arm/arm64 systems when the PMU is
> > specified explicitly as part of the event, e.g.
> >
> > $ ./perf record -e
On Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon wrote:
> It sucks that we haven't noticed this being broken for so long, but I can
> confirm that this fixes the issue:
>
> Acked-by: Will Deacon
> Tested-by Will Deacon
Cheers.
> Any chance we can
On Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon wrote:
> It sucks that we haven't noticed this being broken for so long, but I can
> confirm that this fixes the issue:
>
> Acked-by: Will Deacon
> Tested-by Will Deacon
Cheers.
> Any chance we can get this into 4.14? You'll probably need
On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> Currently, perf record is broken on arm/arm64 systems when the PMU is
> specified explicitly as part of the event, e.g.
>
> $ ./perf record -e armv8_cortex_a53/cpu_cycles/u true
>
> In such cases, perf record fails to open events
On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> Currently, perf record is broken on arm/arm64 systems when the PMU is
> specified explicitly as part of the event, e.g.
>
> $ ./perf record -e armv8_cortex_a53/cpu_cycles/u true
>
> In such cases, perf record fails to open events
On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> Currently, perf record is broken on arm/arm64 systems when the PMU is
> specified explicitly as part of the event, e.g.
>
> $ ./perf record -e armv8_cortex_a53/cpu_cycles/u true
>
> In such cases, perf record fails to open events
On Fri, Oct 06, 2017 at 07:38:22PM +0100, Mark Rutland wrote:
> Currently, perf record is broken on arm/arm64 systems when the PMU is
> specified explicitly as part of the event, e.g.
>
> $ ./perf record -e armv8_cortex_a53/cpu_cycles/u true
>
> In such cases, perf record fails to open events
Currently, perf record is broken on arm/arm64 systems when the PMU is
specified explicitly as part of the event, e.g.
$ ./perf record -e armv8_cortex_a53/cpu_cycles/u true
In such cases, perf record fails to open events unless
perf_event_paranoid is set to -1, even if the PMU in question
Currently, perf record is broken on arm/arm64 systems when the PMU is
specified explicitly as part of the event, e.g.
$ ./perf record -e armv8_cortex_a53/cpu_cycles/u true
In such cases, perf record fails to open events unless
perf_event_paranoid is set to -1, even if the PMU in question
12 matches
Mail list logo