From: Tejun Heo <tj@kernel.org>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: MSI broken in libata?
Date: Sat, 09 Jan 2010 18:11:05 +0900 [thread overview]
Message-ID: <4B484829.6060405@kernel.org> (raw)
In-Reply-To: <64bb37e0912250122n4e0e1842q88c0dad7e99ec6a7@mail.gmail.com>
On 12/25/2009 06:22 PM, Torsten Kaiser wrote:
> As reported in http://lkml.org/lkml/2009/12/19/82 the new MSI support
> for sata_sil24 does not work for me.
> This is still the same with 2.6.33-rc2.
>
> Why I think, this might be a problem within libata:
> * other drivers can use MSI successful on my system (tg3, radeon, hda-intel)
> * happens both in sata_sil24 and sata_nv
> * the count in /proc/interrupts increases for the MSIs assigned to
> sata_sil24/sata_nv, so interrupt delivery seems to work
> * only writing seems to fail
How does it fail? Timeouts? Also, ahci enables MSI by default if
available and works fine on many configurations so I don't think
anything in libata core layer is broken regarding MSI (there just
isn't anything which can break).
Thanks.
--
tejun
next prev parent reply other threads:[~2010-01-09 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 9:22 MSI broken in libata? Torsten Kaiser
2010-01-09 9:11 ` Tejun Heo [this message]
2010-01-10 4:33 ` Torsten Kaiser
2010-01-11 1:15 ` Tejun Heo
2010-01-11 1:39 ` Robert Hancock
2010-01-11 2:17 ` Tejun Heo
2010-01-16 21:58 ` Torsten Kaiser
2010-01-17 19:22 ` Robert Hancock
2010-01-17 21:11 ` Torsten Kaiser
2010-01-18 20:51 ` Torsten Kaiser
2010-01-19 2:03 ` Robert Hancock
2010-01-19 7:00 ` Torsten Kaiser
2010-01-19 20:20 ` Torsten Kaiser
2010-01-20 3:00 ` Robert Hancock
2010-01-20 6:48 ` Torsten Kaiser
2010-01-22 0:53 ` Robert Hancock
2010-01-11 6:44 ` Torsten Kaiser
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=4B484829.6060405@kernel.org \
--to=tj@kernel.org \
--cc=jgarzik@pobox.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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