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: Tue, 08 Mar 2005 23:48:56 +0000	[thread overview]
Message-ID: <422E39E7.2A0666EA@sgi.com> (raw)
In-Reply-To: <4228F250.7C5E2E3C@sgi.com>

"Nguyen, Tom L" wrote:

> On Monday, March 07, 2005 8:41 PM Colin wrote:
> > On Altix systems, we have a set of "Interrupt Registers" in Memory
> Address
> > Space that is initialized to target specific CPUs.  The way we
> > initialize a card's MSI is:
> >
> > 1.  The Target Address is One of these "Interrupt Registers"
> > 2.  The Data Payload is the IRQ plus some special Altix bits.
> >
> > This memory write causes the "Interrupt Chipset" to generate a LINTR
> > message to the configured targeted cpu with the IRQ.  Ofcourse, these
> > registers are Altix Platform specific.  Moreover, we have chunks of
> these
> > registers all over the place.
>
> Your solution is Altix chipset specific. MSI affects other architectures
> too. General solution would almost certainly be a better one.

Hi All,

Yes it is and we are looking for a generic solution.

>
>
> > Is there a more direct mechanism to generate an interrupt(LINTR
> Message)
> > to a Processor?
>
> I agree with Jesse's comment.

Well, unfortunately, we do not send IPI by using the Processor Interrupt Block.
We actually
target a Special Altix Chipset "IPI Interrupt" register that ends up generating
an IPI.  That is why, we
have Platform Specific "send ipi" calls on ia64:

platform_send_ipi()
  File          Line
0 machvec.h     113 #define platform_send_ipi ia64_mv.send_ipi
1 machvec.h     282 #define platform_send_ipi ia64_send_ipi
2 machvec_sn2.h  86 #define platform_send_ipi sn2_send_IPI
3 machvec.h      95 #define platform_send_ipi ia64_mv.send_ipi
4 machvec.h     255 #define platform_send_ipi ia64_send_ipi
5 machvec_sn2.h  83 #define platform_send_ipi sn2_send_IPI

I do not know why we do not use the Processor Interrupt Block, but I will find
out.  But this does
not mean that we cannot use the PIB for MSI.  Ofcourse, it may not be relocated
at
0x0000 0000 FEE0 0000.

>
>
> > With Altix, it's always interesting, with respect to "just work" with
> > typical ia64 code base.  Hopefully, it will work cleaner compared to
> > some of our other efforts.
> >
> > Are you the maintainer for the MSI code?
>
> I suggest you move any discussion or any proposed changes to LKML
> because MSI affects other architectures too. Again, general solution
> would almost certainly be a better one.

We will.  We are looking for a general solution.

We will start looking through the MSI code see how best we can implement
this functionality to support Altix platform.  At that point we will post to
lkml for guidance.

Thanks.

colin

>
>
> Thanks,
> Long
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2005-03-08 23:48 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 [this message]
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
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=422E39E7.2A0666EA@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