linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Li Tony <Tony.Li@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Gala Kumar <kumar.gala@freescale.com>
Subject: RE: [PATCH] Add IPIC MSI interrupt support
Date: Tue, 04 Dec 2007 23:04:18 +1100	[thread overview]
Message-ID: <1196769858.32524.8.camel@concordia> (raw)
In-Reply-To: <995B09A8299C2C44B59866F6391D2635D75588@zch01exm21.fsl.freescale.net>

[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]

On Tue, 2007-12-04 at 18:34 +0800, Li Tony wrote:
> > From: Michael Ellerman [mailto:michael@ellerman.id.au] 
> > Sent: 2007年12月4日 13:38
> > To: Li Tony
> > Cc: Li Tony; Gala Kumar; linuxppc-dev
> > Subject: Re: [PATCH] Add IPIC MSI interrupt support
> > 
> > On Mon, 2007-12-03 at 17:07 +0800, Li Li wrote:
> > > Hi Michael,
> > > 
> > > I emulate mpic to write this IPIC MSI routines. :)
> > > 
> > > 
> > > > > diff --git a/arch/powerpc/platforms/83xx/mpc837x_mds.c 
> > > > > b/arch/powerpc/platforms/83xx/mpc837x_mds.c
> > > > > index 6048f1b..dbea34b 100644
> > > > > --- a/arch/powerpc/platforms/83xx/mpc837x_mds.c
> > > > > +++ b/arch/powerpc/platforms/83xx/mpc837x_mds.c
> > 
> > > > > +
> > > > > +#define	ipic_msi_irq_to_hw(virq)	
> > ((unsigned int)irq_map[virq].hwirq)
> > > > 
> > > > What's wrong with virq_to_hw() ?
> > > > 
> > > 
> > > viqr_to_hw is not __inline__.
> > 
> > Hmm, ok. The three places you use it you also take a spin 
> > lock, so I'm not sure the function call's really going to 
> > kill you performance wise.
> > 
> 
> I am not very sure about spin_lock influence.
> But maybe somebody will change the virq_to_hw implementation.
> I will take virq_to_hw instead. 

I mean the time to take the function call should be pretty small
compared to taking and releasing a spinlock - but if you have
performance numbers to prove otherwise let me know :)

> I see that the virq_to_hw is do inline in 2.6.22.
> Why remove it?

It was made non-inline because modules want to use it, and we didn't
want to export the irq_map to modules as well.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-12-04 12:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30  3:48 [PATCH] Add IPIC MSI interrupt support Li Li
2007-12-03  1:52 ` David Gibson
2007-12-03  4:59   ` Li Li
2007-12-03  4:02 ` Michael Ellerman
2007-12-03  9:07   ` Li Li
2007-12-03 21:03     ` Benjamin Herrenschmidt
2007-12-04  1:41       ` Li Li
2007-12-04  5:38     ` Michael Ellerman
2007-12-04  7:51       ` Benjamin Herrenschmidt
2007-12-04  9:10         ` Li Li
2007-12-04 10:34       ` Li Tony
2007-12-04 12:04         ` Michael Ellerman [this message]
2007-12-04 13:13           ` Scott Wood

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=1196769858.32524.8.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=Tony.Li@freescale.com \
    --cc=kumar.gala@freescale.com \
    --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).