All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [E1000-devel] [PATCH] e1000e: test MSI interrupts
Date: Wed, 26 Mar 2008 13:42:50 -0700	[thread overview]
Message-ID: <47EAB54A.1060306@intel.com> (raw)
In-Reply-To: <47EA9911.8040101@garzik.org>

Jeff Garzik wrote:
> Auke Kok wrote:
>> From: Jesse Brandeburg <jesse.brandeburg@intel.com>
>>
>> Test the MSI interrupt physically once before assuming that it
>> actually works. Several platforms have already come across that
>> have non-functional MSI interrupts and this code will attempt
>> to detect those safely. Once the test succeeds MSI interrupts
>> will be enabled.
>>
>> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
>> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
>> ---
>>
>>  drivers/net/e1000e/defines.h |    1 
>>  drivers/net/e1000e/e1000.h   |    1 
>>  drivers/net/e1000e/netdev.c  |  161 ++++++++++++++++++++++++++++++++++++++++--
>>  3 files changed, 155 insertions(+), 8 deletions(-)
> 
> Ah, the perennial add-same-test-to-every-driver conundrum.
> 
> I think we are far enough along with MSI to _not_ do this anymore in 
> drivers.
> 
> The platforms with MSI problems should be discovered, made public, and 
> worked around.
> 
> Otherwise you hide the same problem, just for someone else to discover 
> with another component of the machine.

ok, that's reasonable as I have not recently seen any "new" reports against the
current trees.

We have to keep this patch in our out-of-tree version around though, since a lot
of distros still ship kernels without all the new MSI quirks. But that's not for
this forum.

Thanks,

Auke


  reply	other threads:[~2008-03-26 20:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 18:36 [PATCH] e1000e: test MSI interrupts Auke Kok
2008-03-26 18:42 ` Jeff Garzik
2008-03-26 20:42   ` Kok, Auke [this message]
2008-03-27 17:53     ` Brandeburg, Jesse
2008-03-27 19:43       ` Jeff Garzik
2008-03-27 22:05         ` David Miller
2008-03-27 22:55           ` Brandeburg, Jesse
2008-03-27 23:06             ` David Miller
2008-03-27 23:38             ` Jeff Garzik
2008-03-27 23:53               ` Kok, Auke
2008-03-28  0:03                 ` David Miller
2008-03-27 21:59       ` David Miller
2008-03-27 22:05       ` Andy Gospodarek
2008-03-27 22:16         ` Kok, Auke
2008-03-27 22:33           ` Andy Gospodarek
2008-03-27 22:47             ` Kok, Auke

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=47EAB54A.1060306@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@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 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.