From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Liu <r63238@freescale.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Kumar Gala <galak@gate.crashing.org>
Subject: Re: fsl booke MM vs. SMP questions
Date: Wed, 23 May 2007 13:08:56 +1000 [thread overview]
Message-ID: <1179889736.32247.893.camel@localhost.localdomain> (raw)
In-Reply-To: <1179887929.3656.2.camel@localhost.localdomain>
On Wed, 2007-05-23 at 10:38 +0800, Dave Liu wrote:
> On Wed, 2007-05-23 at 08:42 +1000, Benjamin Herrenschmidt wrote:
>
> > The IPIs should be buffered by the PIC ... delivered only once but
>
> but what is the buffer depth for IPIs in the PIC?
One :-)
You never "loose" IPIs in the sense that you always get at least 1
interrupt for N IPIs and it's up to software to make sure not to lose
any event. The linux kernel arch code usually handles that with a
synchronous IPI mecanism.
Ben.
next prev parent reply other threads:[~2007-05-23 3:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 7:06 fsl booke MM vs. SMP questions Benjamin Herrenschmidt
[not found] ` <1179741447.3660.7.camel@localhost.localdomain>
[not found] ` <1179742083.32247.689.camel@localhost.localdomain>
2007-05-21 11:37 ` Dave Liu
2007-05-21 22:07 ` Benjamin Herrenschmidt
2007-05-22 3:09 ` Benjamin Herrenschmidt
2007-05-22 10:56 ` Dave Liu
2007-05-22 22:42 ` Benjamin Herrenschmidt
2007-05-23 2:38 ` Dave Liu
2007-05-23 3:08 ` Benjamin Herrenschmidt [this message]
2007-05-28 9:05 ` Liu Dave-r63238
2007-05-28 9:24 ` Benjamin Herrenschmidt
2007-05-28 9:37 ` Liu Dave-r63238
2007-05-28 10:00 ` Benjamin Herrenschmidt
2007-05-28 10:23 ` Gabriel Paubert
2007-05-28 10:28 ` Benjamin Herrenschmidt
2007-05-22 8:46 ` Gabriel Paubert
2007-05-22 9:14 ` Benjamin Herrenschmidt
2007-05-22 10:02 ` Gabriel Paubert
2007-05-22 10:05 ` Benjamin Herrenschmidt
2007-05-23 9:12 ` Gabriel Paubert
2007-05-22 3:03 ` Kumar Gala
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=1179889736.32247.893.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=galak@gate.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=r63238@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.