<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 28.08.2010, at 07:24, Kyle Moffett wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Fri, Aug 27, 2010 at 20:58, Alexander Graf <<a href="mailto:agraf@suse.de">agraf@suse.de</a>> wrote:<br><blockquote type="cite">On 27.08.2010, at 21:06, Kyle Moffett wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">The kvmppc_e500_stlbe_invalidate() function was trying to pass too many<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">parameters to trace_kvm_stlb_inval(). This appears to be a bad<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">copy-paste from a call to trace_kvm_stlb_write().<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Which kernel is this against? That trace point is already commented out in my tree.<br></blockquote><br>Oh, hm, I guess I haven't rebased this patch since 2.6.35-ish. The<br>trace point seems to work correctly with the fixed arguments; if<br>you'll tell me which tree I should base it on I can easily resubmit.<br></div></blockquote><div><br></div><div>My tree is at <a href="git://github.com/agraf/linux-2.6.git">git://github.com/agraf/linux-2.6.git</a> kvm-ppc-next. If you like I'll gladly take a patch in to enable the point again :).</div><div><br></div><div>Alex</div></div><br></body></html>