From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: RE: [PATCH] qe_ic: Do a sync when masking interrupts.
Date: Wed, 25 Oct 2006 13:51:14 +1000 [thread overview]
Message-ID: <1161748274.22582.30.camel@localhost.localdomain> (raw)
In-Reply-To: <4879B0C6C249214CBE7AB04453F84E4D2071C2@zch01exm20.fsl.freescale.net>
On Tue, 2006-10-24 at 15:17 +0800, Li Yang-r58472 wrote:
> > -----Original Message-----
> > From: Scott Wood [mailto:scottwood@freescale.com]
> > Sent: Tuesday, October 24, 2006 2:27 AM
> > To: Segher Boessenkool
> > Cc: mrz5149@acm.org; Li Yang-r58472; Paul Mackerras;
> linuxppc-dev@ozlabs.org
> > Subject: Re: [PATCH] qe_ic: Do a sync when masking interrupts.
> >
> > Segher Boessenkool wrote:
> > > If a sync after an MMIO write is enough, then (in almost all
> > > cases) so is an eieio.
> >
> > In this case, the spurious interrupts still happen with eieio, but not
> > with sync.
>
> eieio on e300 core is just a no-op.
It's not sent to the bus on non-cahed storage (like the PCI bridge ?)
That's pretty bad ... there is quite a bit of code that assumes that
eieio's will prevent write combining...
Ben.
next prev parent reply other threads:[~2006-10-25 3:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 15:30 RE: [PATCH] qe_ic: Do a sync when masking interrupts Michael R. Zucca
2006-10-23 16:49 ` Segher Boessenkool
2006-10-23 18:27 ` Scott Wood
2006-10-23 18:46 ` Segher Boessenkool
2006-10-24 7:17 ` Li Yang-r58472
2006-10-25 3:51 ` Benjamin Herrenschmidt [this message]
2006-10-25 4:47 ` Liu Dave-r63238
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 18:53 Scott Wood
2006-10-19 18:03 Scott Wood
2006-10-20 3:03 ` Li Yang-r58472
2006-10-23 3:59 ` Paul Mackerras
2006-10-23 9:35 ` Li Yang-r58472
2006-10-23 15:19 ` Scott Wood
2006-10-23 15:29 ` Scott Wood
2006-10-23 17:52 ` Kumar Gala
2006-10-23 18:22 ` 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=1161748274.22582.30.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=LeoLi@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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.