From: "Shawn Jin" <shawnxjin@gmail.com>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: MSI support on Linux PCI implementation for Ocotea
Date: Fri, 16 Jun 2006 14:45:21 -0700 [thread overview]
Message-ID: <c3d0340b0606161445w5acb4da8j26870f56a4bf4d9@mail.gmail.com> (raw)
In-Reply-To: <1150413771.7725.20.camel@localhost.localdomain>
Hi Ben,
> Now, regarding MSI, as you have noticed, the situation isn't great. I'm
> currently in the middle of reworking our interrupt management (and
> interrupt numbers allocation layer) and Michael Ellermann is looking at
> the MSI issue in parallel.
Just one point about MSI(-X) message address and data format. I think
it should be the platform that defines the content. Current
implementation doesn't have this flexibility. We have a design where
MSI mode uses message data to carry vector number info while MSI-X
mode uses message address to carry this info. Although it seems
strange, but I think it's allowed by the spec.
Thanks,
-Shawn.
next prev parent reply other threads:[~2006-06-16 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 21:14 MSI support on Linux PCI implementation for Ocotea Shawn Jin
2006-06-15 23:22 ` Benjamin Herrenschmidt
2006-06-15 23:31 ` Roland Dreier
2006-06-16 0:45 ` Shawn Jin
2006-06-16 21:45 ` Shawn Jin [this message]
2006-06-16 22:13 ` Benjamin Herrenschmidt
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=c3d0340b0606161445w5acb4da8j26870f56a4bf4d9@mail.gmail.com \
--to=shawnxjin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).