From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] PCI MSI Kconfig consolidation
Date: Tue, 13 Apr 2004 20:08:17 +0000 [thread overview]
Message-ID: <200404131408.17248.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E502404058232@orsmsx404.jf.intel.com>
On Tuesday 13 April 2004 1:16 pm, Nguyen, Tom L wrote:
> On Tuesday, April 13, Bjorn Helgaas wrote:
>
> > This consolidates the PCI MSI configuration into drivers/pci/Kconfig,
> > removing it from the i386, x86_64, and ia64 Kconfig.
> >
> > It also changes the default for ia64 from "y" to "n". The default on
> > i386 is "n" already, and I'm not sure why ia64 should be different.
>
> It looks good; however, it may create a confusion on ia64 because ia64
> is already vector-based indexing.
No. This is one reason why I think the MSI configuration symbol
should be CONFIG_PCI_MSI, not CONFIG_PCI_USE_VECTOR.
The fact that external interrupts in the ia64 architecture include a
number, and that we happen to call that number a "vector", has
nothing to do with PCI MSI.
In fact, I think there's a whole lot more architecture-specific
knowledge that has leaked across into drivers/pci/msi.[ch]. For
example, the MSI capability basically defines just a message address
register and a message data register. It does not define anything
about the interpretation of either address or data. So all the stuff
in struct msg_data and struct msg_address (vector, delivery_mode,
level, trigger, dest_id, dest_mode, redirection_hint) looks to me
like Intel-specific knowledge that should be encapsulated in the
arch code.
next prev parent reply other threads:[~2004-04-13 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 16:41 [PATCH] PCI MSI Kconfig consolidation Bjorn Helgaas
2004-04-13 18:37 ` Andi Kleen
2004-04-13 19:16 ` Nguyen, Tom L
2004-04-13 20:08 ` Bjorn Helgaas [this message]
2004-04-13 21:29 ` Andi Kleen
2004-04-13 20:09 ` Grant Grundler
2004-04-13 21:54 ` Nguyen, Tom L
2004-04-13 21:57 ` Nguyen, Tom L
2004-04-15 20:49 ` Nguyen, Tom L
2004-04-16 0:41 ` Bjorn Helgaas
2004-04-16 15:15 ` Nguyen, Tom L
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=200404131408.17248.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=ak@suse.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.l.nguyen@intel.com \
/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