From: Roland Dreier <roland@topspin.com>
To: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Question on using MSI in PCI driver
Date: Tue, 22 Jun 2004 10:49:32 -0700 [thread overview]
Message-ID: <52llifo53n.fsf@topspin.com> (raw)
In-Reply-To: <C7AB9DA4D0B1F344BF2489FA165E5024057E4E7B@orsmsx404.amr.corp.intel.com> (Tom L. Nguyen's message of "Tue, 22 Jun 2004 08:24:02 -0700")
Tom> The PCI 3.0 specification has implementation notes that MMIO
Tom> address space for a device's MSI-X structure should be
Tom> isolated so that the software system can set different page
Tom> for controlling accesses to the MSI-X structure. The
Tom> implementation of MSI patch requires the PCI subsystem, not a
Tom> device driver, to maintain full control of the MSI-X
Tom> table/MSI-X PBA and MMIO address space of the MSI-X
Tom> table/MSI-X PBA. A device driver is prohibited from
Tom> requesting the MMIO address space of the MSI-X table/MSI-X
Tom> PBA. Otherwise, the PCI subsystem will fail enabling MSI-X on
Tom> its hardware device when it calls the function
Tom> pci_enable_msi().
Thanks. I guess for the time being I will have to split up my request
region calls.
Do you think the msi subsystem should use a different name for the
MSI-X memory region ("MSI-X iomap Failure" seems very strange to me).
- Roland
next prev parent reply other threads:[~2004-06-22 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 15:24 Question on using MSI in PCI driver Nguyen, Tom L
2004-06-22 17:49 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-22 18:43 Nguyen, Tom L
2004-06-22 18:08 Nguyen, Tom L
2004-06-22 18:26 ` Roland Dreier
2004-06-22 19:51 ` Christoph Hellwig
2004-06-22 19:55 ` Roland Dreier
2004-06-22 2:22 Roland Dreier
2004-06-22 3:50 ` Jeff Garzik
2004-06-22 3:54 ` Roland Dreier
2004-06-22 4:01 ` Jeff Garzik
2004-06-22 4:04 ` 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=52llifo53n.fsf@topspin.com \
--to=roland@topspin.com \
--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