From: Ingo Molnar <mingo@elte.hu>
To: kus Kusche Klaus <kus@keba.com>
Cc: stern@rowland.harvard.edu, linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.11, USB: High latency?
Date: Mon, 4 Apr 2005 10:36:52 +0200 [thread overview]
Message-ID: <20050404083652.GA29525@elte.hu> (raw)
In-Reply-To: <AAD6DA242BC63C488511C611BD51F3673231DD@MAILIT.keba.co.at>
* kus Kusche Klaus <kus@keba.com> 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
next prev parent reply other threads:[~2005-04-04 8:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 8:03 2.6.11, USB: High latency? kus Kusche Klaus
2005-04-04 8:36 ` Ingo Molnar [this message]
2005-04-04 19:40 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 13:16 kus Kusche Klaus
2005-04-01 13:41 ` Ingo Molnar
2005-04-01 6:46 kus Kusche Klaus
2005-04-01 17:20 ` Alan Stern
2005-03-31 12:12 kus Kusche Klaus
2005-03-31 11:15 kus Kusche Klaus
2005-03-31 16:48 ` Alan Stern
2005-03-30 22:57 David Brownell
2005-03-31 0:43 ` Lee Revell
2005-03-31 1:13 ` David Brownell
2005-03-31 1:21 ` Lee Revell
2005-03-31 1:32 ` David Brownell
2005-03-31 0:51 ` Lee Revell
2005-03-31 1:28 ` David Brownell
2005-03-31 1:32 ` Lee Revell
2005-03-31 1:40 ` David Brownell
2005-03-31 1:44 ` Lee Revell
2005-03-31 1:39 ` Lee Revell
2005-03-30 13:51 kus Kusche Klaus
2005-03-30 15:55 ` Alan Stern
2005-03-30 21:28 ` Lee Revell
2005-03-31 11:30 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050404083652.GA29525@elte.hu \
--to=mingo@elte.hu \
--cc=kus@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox