Hi,
On Fri, Jul 10, 2015 at 1:35 AM, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
>> On Thu, Jul 09, 2015 at 02:32:05PM +0200, Ingo Molnar wrote:
>> >
>> >perf record error: The 'bts' PMU is not available, because the CPU does
>> > not support it
>>
>> This one makes sense.
>>
>> >p
* Peter Zijlstra wrote:
> On Thu, Jul 09, 2015 at 02:32:05PM +0200, Ingo Molnar wrote:
> >
> >perf record error: The 'bts' PMU is not available, because the CPU does
> > not support it
>
> This one makes sense.
>
> >perf record error: The 'bts' PMU is not available, because this
> >
Em Thu, Jul 09, 2015 at 02:42:57PM +0200, Peter Zijlstra escreveu:
> On Thu, Jul 09, 2015 at 02:32:05PM +0200, Ingo Molnar wrote:
> >perf record error: The 'bts' PMU is not available, because the CPU does
> > not support it
> This one makes sense.
> >perf record error: The 'bts' PMU i
On Thu, Jul 09, 2015 at 02:32:05PM +0200, Ingo Molnar wrote:
>
>perf record error: The 'bts' PMU is not available, because the CPU does
> not support it
This one makes sense.
>perf record error: The 'bts' PMU is not available, because this
> architecture does not support it
>perf r
* Peter Zijlstra wrote:
> On Thu, Jul 09, 2015 at 11:26:56AM +0200, Ingo Molnar wrote:
> >
> > * Peter Zijlstra wrote:
> >
> > > On Thu, Jul 09, 2015 at 10:48:00AM +0300, Adrian Hunter wrote:
> > >
> > > > Known PMUs may not be present for various reasons. Provide a way for
> > > > the user
On Thu, Jul 09, 2015 at 11:26:56AM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > On Thu, Jul 09, 2015 at 10:48:00AM +0300, Adrian Hunter wrote:
> >
> > > Known PMUs may not be present for various reasons. Provide a way for the
> > > user
> > > to know what the reason is.
> >
> >
On Thu, Jul 09, 2015 at 12:30:30PM +0300, Adrian Hunter wrote:
> On 09/07/15 11:50, Peter Zijlstra wrote:
> > Can we limit it to PMUs for which we've (attempted to) load the drivers?
> > That would obviously make a few of your status bits redundant, but then
> > you've not explained why we're inte
On 09/07/15 11:50, Peter Zijlstra wrote:
> On Thu, Jul 09, 2015 at 10:48:00AM +0300, Adrian Hunter wrote:
>> Known PMUs may not be present for various reasons.
>> Provide a way for the user to know what the reason
>> is.
>
> Not a bad idea, but I do wonder where we should draw the line on what is
* Peter Zijlstra wrote:
> On Thu, Jul 09, 2015 at 10:48:00AM +0300, Adrian Hunter wrote:
>
> > Known PMUs may not be present for various reasons. Provide a way for the
> > user
> > to know what the reason is.
>
> Not a bad idea, but I do wonder where we should draw the line on what is
> 'kno
On Thu, Jul 09, 2015 at 10:48:00AM +0300, Adrian Hunter wrote:
> Known PMUs may not be present for various reasons.
> Provide a way for the user to know what the reason
> is.
Not a bad idea, but I do wonder where we should draw the line on what is
'known'. The patch as proposed will have bts/pt li
On 09/07/15 11:10, Ingo Molnar wrote:
>
> * Adrian Hunter wrote:
>
>> Known PMUs may not be present for various reasons.
>> Provide a way for the user to know what the reason
>> is.
>>
>> A bus attribute is created for each known PMU beneath
>> a group "known_pmus". The attribute name is the sa
* Adrian Hunter wrote:
> Known PMUs may not be present for various reasons.
> Provide a way for the user to know what the reason
> is.
>
> A bus attribute is created for each known PMU beneath
> a group "known_pmus". The attribute name is the same
> as the PMU name. The value is a string cons
Known PMUs may not be present for various reasons.
Provide a way for the user to know what the reason
is.
A bus attribute is created for each known PMU beneath
a group "known_pmus". The attribute name is the same
as the PMU name. The value is a string consisting of
one or, optionally, two parts:
13 matches
Mail list logo
