From: Grant Grundler <iod00d@hp.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Greg KH <gregkh@suse.de>, Mark Maule <maule@sgi.com>,
"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
shaohua.li@intel.com
Subject: Re: [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register
Date: Thu, 16 Mar 2006 15:45:21 -0800 [thread overview]
Message-ID: <20060316234521.GC9746@esmail.cup.hp.com> (raw)
In-Reply-To: <adalkvaneq5.fsf@cisco.com>
On Thu, Mar 16, 2006 at 03:37:22PM -0800, Roland Dreier wrote:
> I think we really want to make drivers/pci/msi.c less platform-specific.
> Both powerpc and sparc64 are starting to pay attention to MSI, so we
> should really be trying to move things in the direction of a clean
> separation of generic MSI handling and Intel-specific bits.
Matthew Wilcox and I have previously volunteered to get MSI working
on parisc arch. parisc, like systems with Local SAPIC, only
operates on transaction based interrupts at the CPU level.
We need an arch hook to set the target address of the CPU
instead of looking at ID/EID bits but haven't proposed
anything concrete yet. My understanding is SGI needs the
same thing for Altix/SN2 platforms.
thanks,
grant
next prev parent reply other threads:[~2006-03-16 23:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 21:01 [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register Jun'ichi Nomura
2006-03-14 21:45 ` Andrew Morton
2006-03-14 21:59 ` Greg KH
2006-03-14 22:25 ` Matthew Wilcox
2006-03-15 0:51 ` Jun'ichi Nomura
2006-03-15 23:55 ` Greg KH
2006-03-16 15:19 ` Jun'ichi Nomura
2006-03-16 18:19 ` Mark Maule
2006-03-16 19:32 ` Jun'ichi Nomura
2006-03-16 19:41 ` Mark Maule
2006-03-16 23:28 ` Greg KH
2006-03-16 23:37 ` Roland Dreier
2006-03-16 23:45 ` Grant Grundler [this message]
2006-03-16 23:47 ` Greg KH
2006-03-16 23:41 ` Grant Grundler
2006-03-16 23:49 ` Greg KH
2006-03-17 0:41 ` Grant Grundler
2006-03-17 1:18 ` Mark Maule
2006-03-16 15:29 ` Jun'ichi Nomura
2006-03-14 21:57 ` Adrian Bunk
2006-03-14 23:55 ` Jun'ichi Nomura
2006-03-15 0:09 ` Mark Maule
2006-03-15 1:04 ` Jun'ichi Nomura
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=20060316234521.GC9746@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maule@sgi.com \
--cc=rdreier@cisco.com \
--cc=shaohua.li@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