From: Roland Dreier <roland@topspin.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Tom L Nguyen <tom.l.nguyen@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: MSI to memory?
Date: Fri, 02 Jul 2004 09:04:12 -0700 [thread overview]
Message-ID: <52isd68kg3.fsf@topspin.com> (raw)
In-Reply-To: <200407011215.59723.bjorn.helgaas@hp.com> (Bjorn Helgaas's message of "Thu, 1 Jul 2004 12:15:59 -0600")
Bjorn> The conventional use of MSI is for a PCI adapter to
Bjorn> generate processor interrupts by writing to a local APIC.
Bjorn> But I've seen some things that lead me to believe it would
Bjorn> also allow an adapter to write to things other than a local
Bjorn> APIC, i.e., to memory.
Bjorn> If so, is that a useful capability that should be exposed
Bjorn> through the Linux MSI interface?
MSI does allow an adapter to write messages to any arbitrary PCI
address (under the control of the host software). It's not clear to
me that write to anywhere other than a special interrupt generation
address is that useful.
It is true that the current Linux MSI code is quite Intel-specific,
hard-coding Intel addresses and message contents. At some point, if
I'm able to get documentation on interesting hardware, I would like to
try and move the generation of addresses/messages to arch-specific
code so that Linux can support more general PCI hosts.
Unfortunately, it seems that at least the current HyperTransport PCI-X
tunnels used on Opteron systems do not support MSI (based on my quick
reading of the documentation). The only hardware I have access to
that supports MSI is the PowerPC 440GP, and I'm not sure how
interesting that is.
I assume that future PCI Express chipsets for Opteron will support
MSI, and hopefully documentation will be available (or manufacturers
will write Linux support).
Does anyone know if there are any ppc64 systems that support MSI?
Thanks,
Roland
prev parent reply other threads:[~2004-07-02 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 18:15 MSI to memory? Bjorn Helgaas
2004-07-01 18:53 ` Rajesh Shah
2004-07-02 15:51 ` Bjorn Helgaas
2004-07-07 12:31 ` Davide Rossetti
2004-07-07 12:45 ` Helge Hafting
2004-07-07 16:59 ` Roland Dreier
2004-07-08 9:03 ` Helge Hafting
2004-07-07 17:04 ` Zwane Mwaikambo
2004-07-07 13:15 ` Richard B. Johnson
2004-07-07 17:13 ` Rajesh Shah
2004-07-02 16:04 ` Roland Dreier [this message]
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=52isd68kg3.fsf@topspin.com \
--to=roland@topspin.com \
--cc=bjorn.helgaas@hp.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