linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: davem@redhat.com, willy@debian.org,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Message Signalled Interrupt support?
Date: Mon, 12 May 2003 13:26:54 -0400	[thread overview]
Message-ID: <200305121330_MC3-1-3881-E571@compuserve.com> (raw)

Jeff Garzik wrote:

> Has anybody done any work, or put any thought, into MSI support?
> 
> Would things massively break if I set up MSI manually in the driver?
> 
> I heard rumblings on lkml that Intel has done some work internally w/
> MSI support in Linux, but that doesn't help me much without further
> details ;-)


I found this in my archives:

================================

Subject: RE: [PATCH] 2.5.68 Fix IO_APIC IRQ assignment bug
Date: Mon, 21 Apr 2003 09:34:34 -0700
From: "Nakajima, Jun" <jun.nakajima@intel.com>

<SNIP>

After (vector-based)
           CPU0       CPU1       
  0:     709682          0    IO-APIC-edge  timer
  2:          0          0          XT-PIC  cascade
  9:          0          0   IO-APIC-level  acpi
 14:       4988          1    IO-APIC-edge  ide0
 15:         10          1    IO-APIC-edge  ide1
177:         78          0   IO-APIC-level  uhci-hcd
185:          0          0   IO-APIC-level  uhci-hcd, uhci-hcd
193:         58          0   IO-APIC-level  uhci-hcd
201:          0          0   IO-APIC-level  ehci-hcd
209:        356          0   IO-APIC-level  eth0
NMI:          0          0 
LOC:     707613     707524 
ERR:          0
MIS:          0

=========================================

  They changed things so the MSI scheme uses the vector number
directly instead of remapping it...




             reply	other threads:[~2003-05-12 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 17:26 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 18:26 Message Signalled Interrupt support? Nakajima, Jun
2003-05-12 17:53 Nakajima, Jun
2003-05-12 16:32 Jeff Garzik
2003-05-12 16:53 ` Matthew Wilcox
2003-05-12 17:20   ` David S. Miller
2003-05-12 18:54     ` Mika Penttilä
2003-05-12 17:43   ` Matt Porter
2003-05-12 18:20     ` Matthew Wilcox
2003-05-12 18:48       ` Matt Porter
2003-05-13 11:21         ` Ivan Kokshaysky

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=200305121330_MC3-1-3881-E571@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=davem@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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;
as well as URLs for NNTP newsgroup(s).