From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>
Subject: Re: MSI and driver APIs
Date: Fri, 16 Dec 2005 08:18:17 +1100 [thread overview]
Message-ID: <1134681498.16880.39.camel@gaston> (raw)
In-Reply-To: <adaek4enjoz.fsf@cisco.com>
On Thu, 2005-12-15 at 13:18 -0800, Roland Dreier wrote:
> Benjamin> You can have multiple MSIs too (they just have to be
> Benjamin> contiguous in numbers and aligned on the nearest power
> Benjamin> of 2).
>
> Good point. I just got too used to the x86-ism of the current MSI
> code, which can't handle allocating contiguous vectors.
>
> Benjamin> I'm tempted to leave them enabled and only disable them
> Benjamin> when request_irq() is done on the legacy INTx... Does
> Benjamin> anybody see a problem with this approach ?
>
> You might run into trouble on hardware (think tg3 or its ilk again)
> where you might have to do something beyond disabling MSI in the PCI
> header to switch the chip out of MSI mode.
But won't the driver call pci_enable/disable_msi() in those cases ? If
not, it's easy enough to add (explicit disable rather than not-enabled).
I'm mostly concerned about "dumb" drivers that don't know about MSI at
all...
Ben.
next prev parent reply other threads:[~2005-12-15 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 3:38 Benjamin Herrenschmidt
2005-12-15 21:07 ` Roland Dreier
2005-12-15 21:08 ` Benjamin Herrenschmidt
2005-12-15 21:18 ` Roland Dreier
2005-12-15 21:18 ` Benjamin Herrenschmidt [this message]
2005-12-15 21:36 ` Roland Dreier
2005-12-15 21:42 ` David S. Miller
2005-12-15 21:56 ` Benjamin Herrenschmidt
2005-12-16 0:51 ` Greg KH
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=1134681498.16880.39.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=rdreier@cisco.com \
/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
all inboxes | Powered by JetHome®