On 30.08.2010, at 17:38, Kyle Moffett wrote:
> The kvmppc_e500_stlbe_invalidate() function was trying to pass too many
> parameters to trace_kvm_stlb_inval(). This appears to be a bad
> copy-paste from a call to trace_kvm_stlb_write().
>
> Signed-off-by: Kyle Moffett
Thanks, applied.
Alex
_
The kvmppc_e500_stlbe_invalidate() function was trying to pass too many
parameters to trace_kvm_stlb_inval(). This appears to be a bad
copy-paste from a call to trace_kvm_stlb_write().
Signed-off-by: Kyle Moffett
---
Alex,
This is the rebased patch to re-enable the tracepoint.
I also pushed a
On 28.08.2010, at 07:24, Kyle Moffett wrote:
> On Fri, Aug 27, 2010 at 20:58, Alexander Graf wrote:
>> On 27.08.2010, at 21:06, Kyle Moffett wrote:
>>> The kvmppc_e500_stlbe_invalidate() function was trying to pass too many
>>> parameters to trace_kvm_stlb_inval(). This appears to be a bad
>>>
On Fri, Aug 27, 2010 at 20:58, Alexander Graf wrote:
> On 27.08.2010, at 21:06, Kyle Moffett wrote:
>> The kvmppc_e500_stlbe_invalidate() function was trying to pass too many
>> parameters to trace_kvm_stlb_inval(). This appears to be a bad
>> copy-paste from a call to trace_kvm_stlb_write().
>
>
On 27.08.2010, at 21:06, Kyle Moffett wrote:
> The kvmppc_e500_stlbe_invalidate() function was trying to pass too many
> parameters to trace_kvm_stlb_inval(). This appears to be a bad
> copy-paste from a call to trace_kvm_stlb_write().
Which kernel is this against? That trace point is already c
The kvmppc_e500_stlbe_invalidate() function was trying to pass too many
parameters to trace_kvm_stlb_inval(). This appears to be a bad
copy-paste from a call to trace_kvm_stlb_write().
Signed-off-by: Kyle Moffett
---
arch/powerpc/kvm/e500_tlb.c |3 +--
1 files changed, 1 insertions(+), 2 de