From: Roland Dreier <roland@topspin.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [broken?] Add MSI support to e1000
Date: Mon, 23 Aug 2004 11:26:30 -0700 [thread overview]
Message-ID: <52acwlvhgp.fsf@topspin.com> (raw)
In-Reply-To: <m3oel1hg77.fsf@averell.firstfloor.org> (Andi Kleen's message of "Mon, 23 Aug 2004 20:17:32 +0200")
Andi> There seems to be something wrong with the MSI code in the
Andi> kernel. I tried to add MSI support to the s2io driver on
Andi> x86-64, but it just didn't work (/proc/interrupts still
Andi> displayed IO-APIC mode). I haven't investigated in detail
Andi> yet though.
Hmm... I've not tried MSI on x86-64 (although I have tried it on
Nocona running a 32-bit kernel). I have successfully used both MSI
and MSI-X on i386 with my mthca (InfiniBand HCA) driver, although with
some occasional stability glitches, which may be connected to the
e1000 problem I'm seeing. In any case, /proc/interrupts definitely
shows "PCI-MSI" mode with a non-zero number of interrupts delivered
with my patched e1000 driver.
- Roland
next prev parent reply other threads:[~2004-08-23 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2wpoS-1ai-1@gated-at.bofh.it>
[not found] ` <2wqXF-2jm-29@gated-at.bofh.it>
2004-08-23 18:17 ` [PATCH] [broken?] Add MSI support to e1000 Andi Kleen
2004-08-23 18:26 ` Roland Dreier [this message]
2004-08-24 17:40 Nguyen, Tom L
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 16:01 Nguyen, Tom L
2004-08-23 23:17 Nguyen, Tom L
2004-08-24 2:15 ` Roland Dreier
2004-08-23 19:41 Nguyen, Tom L
2004-08-23 23:39 ` Andi Kleen
2004-08-24 14:19 ` Roland Dreier
2004-08-23 19:09 Nguyen, Tom L
2004-08-23 19:39 ` Roland Dreier
2004-08-23 15:41 Nguyen, Tom L
2004-08-23 17:25 ` Roland Dreier
2004-08-24 21:49 ` Chris Leech
2004-08-24 23:36 ` Roland Dreier
2004-08-20 21:37 Roland Dreier
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=52acwlvhgp.fsf@topspin.com \
--to=roland@topspin.com \
--cc=ak@muc.de \
--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 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.