From: Greg KH <greg@kroah.com>
To: Keith Packard <keithp@keithp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-usb@vger.kernel.org
Subject: Re: USB interrupt handler routine
Date: Sat, 13 Dec 2008 20:41:12 -0800 [thread overview]
Message-ID: <20081214044112.GA28733@kroah.com> (raw)
In-Reply-To: <1229056537.4137.10.camel@aiko.keithp.com>
<added linux-usb list, that's the proper place for it...)
On Thu, Dec 11, 2008 at 08:35:37PM -0800, Keith Packard wrote:
> We recently made a patch in the Intel DRM driver:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b60678a75d44fa9d5969f79781bd856ad5858609
>
> This switches from non-MSI to MSI-mode.
>
> It "should" have had no effect, but our concern is that what we're
> really seeing is interrupt sharing troubles. We've had several people
> say that they got an interrupt flood when plugging in a USB stick or
> external disk. Switching the graphics driver to MSI mode "cures" the
> bug, but that sure seems like a work-around rather than a bug fix to me.
>
> When our driver is active, it can generate a lot of interrupts,
> potentially thousands per second. Is it possible that the UHCI or EHCI
> drivers could get confused if checking for interrupt status this often?
>
> Eric noted that the USB driver appears to not check and ACK interrupt
> status unconditionally, preferring to check the software state
> beforehand. I'm wondering if this may open up a potential race between
> hardware state change and ISR bit setting.
Check what software state? It shouldn't cause any race issues, but I'll
defer to David and Alan to concur this or not.
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-14 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 4:35 USB interrupt handler routine Keith Packard
2008-12-14 4:41 ` Greg KH [this message]
2008-12-14 15:50 ` Alan Stern
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=20081214044112.GA28733@kroah.com \
--to=greg@kroah.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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