All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	linux-kernel@vger.kernel.org, akpm@osdl.org, greg@kroah.com,
	linux-pci@atrey.karlin.mff.cuni.cz, ak@suse.de
Subject: Re: [PATCH] MSI interrupts: disallow when no LAPIC/IOAPIC support
Date: Tue, 27 Sep 2005 09:51:03 -0600	[thread overview]
Message-ID: <20050927155103.GA9294@colo.lackof.org> (raw)
In-Reply-To: <17209.3427.936263.463751@alkaid.it.uu.se>

On Tue, Sep 27, 2005 at 11:14:11AM +0200, Mikael Pettersson wrote:
> Grant Grundler writes:
>  > Yeah, my preference would be PCI_MSI only depend on Local APIC.
>  > (Note that having a Local APIC implies having an IO APIC as well
> 
> Not true. Lots of systems have a local APIC but no I/O APICs.

Eh?!!!
Do systems with Local APIC still have IRQ lines going to the CPU?
How does PCI IRQ line otherwise generate an interrupt?

> However, having an I/O APIC pretty much implies having a local APIC.

Ok - That sounds right for x86 and is true for ia64.
parisc has IO SAPICs but no local APIC.

parisc and (IIRC) alpha has the functional equivalent of Local APIC
but the implementation details are different. ie they can't share
code with x86/ia64.

thanks,
grant

  reply	other threads:[~2005-09-27 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27  3:11 [PATCH] MSI interrupts: disallow when no LAPIC/IOAPIC support Randy.Dunlap
2005-09-27  4:48 ` Grant Grundler
2005-09-27  4:52   ` Randy.Dunlap
2005-09-27  5:21     ` Grant Grundler
2005-09-27  9:14       ` Mikael Pettersson
2005-09-27 15:51         ` Grant Grundler [this message]
2005-09-27  9:11     ` Mikael Pettersson
2005-09-27 21:26   ` Jeff Garzik
2005-09-27 22:37     ` Alan Cox
2005-09-29  3:34       ` Grant Grundler
2005-09-29 20:09         ` Eric W. Biederman

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=20050927155103.GA9294@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mikpe@csd.uu.se \
    --cc=rdunlap@xenotime.net \
    /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.