public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Colin Ngam <cngam@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: PCI Express
Date: Wed, 09 Mar 2005 17:42:39 +0000	[thread overview]
Message-ID: <422F358F.5010307@sgi.com> (raw)
In-Reply-To: <4228F250.7C5E2E3C@sgi.com>

Grant Grundler wrote:

>On Wed, Mar 09, 2005 at 08:35:00AM -0800, Nguyen, Tom L wrote:
>  
>
>>Existing MSI support implements a direct
>>memory-write mechanism (generic solution without platform dependency and
>>limitation to MSI-X support as an example). With existing direct
>>memory-write mechanism, a device's MSI address is configured with
>>current running CPU as a target.
>>    
>>
>
>At some point, PARISC (and Alpha?) will also want to support MSI
>using "direct memory write". But like Altix, does not implement
>0xfeeXXXXX (1) PIB since PARISC arch predates PCI by a decade or so.
>
>We'll have to figure out which platform specific hooks would enable
>parisc/alpha/altix to use existing PCI MSI/MSI-X support.
>
Hi Grant,

Sounds great.

Thanks.

colin

>
>PA-RISC IPI is as straight forward as Jesse described - just write
>to a per CPU address with a data value (vector).
>
>thanks,
>grant
>
>(1) the most recent two or three PA-RISC chipsets do implement 0xfeeXXXXX
>interrupt block. But firmware hands us the CPU "ID/EID" values to use
>when programming the IO SAPIC IRT. See drivers/parisc/iosapic.c
>iosapic_set_irt_data() for more details.
>
>Bottomline is, even if we know it's implemented in HW, we don't know if
>we are using 0xfeeXXXXX or not for IO SAPIC today. platform hooks
>into MSI code would have to sort that out.
>  
>



  parent reply	other threads:[~2005-03-09 17:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 23:42 PCI Express Colin Ngam
2005-03-07 16:48 ` Grant Grundler
2005-03-07 16:50 ` Matthew Wilcox
2005-03-07 17:02 ` Mark Maule
2005-03-07 17:21 ` Matthew Wilcox
2005-03-07 20:40 ` Colin Ngam
2005-03-07 23:03 ` Nguyen, Tom L
2005-03-07 23:11 ` Jesse Barnes
2005-03-07 23:31 ` Grant Grundler
2005-03-07 23:32 ` Nguyen, Tom L
2005-03-07 23:36 ` Grant Grundler
2005-03-07 23:40 ` Jesse Barnes
2005-03-07 23:50 ` Grant Grundler
2005-03-08  4:40 ` Colin Ngam
2005-03-08 16:45 ` Jesse Barnes
2005-03-08 19:29 ` Nguyen, Tom L
2005-03-08 23:48 ` Colin Ngam
2005-03-09  0:02 ` Jesse Barnes
2005-03-09  0:13 ` Colin Ngam
2005-03-09  1:29 ` Colin Ngam
2005-03-09  1:29 ` Jesse Barnes
2005-03-09  1:35 ` Colin Ngam
2005-03-09  3:04 ` Grant Grundler
2005-03-09 15:45 ` Colin Ngam
2005-03-09 16:35 ` Nguyen, Tom L
2005-03-09 17:33 ` Grant Grundler
2005-03-09 17:42 ` Colin Ngam [this message]
2005-03-09 17:56 ` Grant Grundler
2005-03-09 18:12 ` Colin Ngam
2005-03-09 18:48 ` Grant Grundler
2005-03-09 19:43 ` Nguyen, Tom L
2005-03-09 21:44 ` Colin Ngam

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=422F358F.5010307@sgi.com \
    --to=cngam@sgi.com \
    --cc=linux-ia64@vger.kernel.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