All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Greg KH <greg@kroah.com>, Andi Kleen <ak@suse.de>,
	linux-pci@atrey.karlin.mff.cuni.cz, acurrid@nvidia.com,
	amartin@nvidia.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: MSI failure on Nvidia nForce
Date: Tue, 18 Apr 2006 14:37:44 -0400	[thread overview]
Message-ID: <444531F8.3040109@garzik.org> (raw)
In-Reply-To: <20060418111944.6ed0505e@localhost.localdomain>

Stephen Hemminger wrote:
> I got a report of sky2 driver irq test failing on x86_64 using
> the following configuration.  Is this a known problem?
> Should workaround be done at PCI layer?
> 
> What the driver does is setup MSI handler, then do a software generated
> IRQ and check that it was received (similar to tg3).  If IRQ test fails
> it falls back to INTx.

Please describe precisely -how- it fails.

pci_enable_msi() does not fail properly on systems that do not support 
MSI.  This is a major unresolved problem that is preventing MSI 
deployment, and causing every driver writer to include a does-MSI-work 
test in their driver.

We need to find a good generic test, or if that fails, adopt an 
ACPI-like rule:  whitelist systems with working MSI before $X date, and 
blacklist systems with broken MSI after $X date.

	Jeff



       reply	other threads:[~2006-04-18 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060418111944.6ed0505e@localhost.localdomain>
2006-04-18 18:37 ` Jeff Garzik [this message]
2006-04-18 18:48   ` MSI failure on Nvidia nForce Stephen Hemminger

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=444531F8.3040109@garzik.org \
    --to=jeff@garzik.org \
    --cc=acurrid@nvidia.com \
    --cc=ak@suse.de \
    --cc=amartin@nvidia.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=shemminger@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.