* kus Kusche Klaus <[EMAIL PROTECTED]> wrote:
> Moreover, we know from experience that the "WBINDV" instruction (Write
> back and invalidate CPU cache) can cause such latencies.
>
> Does this instruction occur anywhere in Linux?
yes, they rarely occur when MTRR's are set (and some drivers like video
uses it too), but then they'd also show up in the trace. The only other
possibility would be if a driver used wbinvd in a preemptible section -
that would not be traced. OTOH, it could still show up in wakeup-latency
tracing.
To make sure, could you remove all relevant wbinvd's from your kernel
tree? You can just comment out those lines from all relevant 'grep -rl
wbinvd . | grep -v x86_64' files. (and in assembly defines, just replace
the "wbinvd" with "nop") The kernel will most likely still work most of
the time.
Or if you want to be safe: change all wbinvd occurances to:
preempt_disable(); <wbinvd>; preempt_enable() sections, for tracing to
pick them up.
Ingo
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
