From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] qe_ic: Do a sync when masking interrupts.
Date: Mon, 23 Oct 2006 10:19:12 -0500 [thread overview]
Message-ID: <453CDD70.9010100@freescale.com> (raw)
In-Reply-To: <17724.15919.790114.628418@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Hmmm. In general a sync having completed doesn't mean that previous
> MMIO stores have actually got to the device. Reading from a device
> register generally does ensure that previous writes have actually got
> to the device though - could you do that instead? I'm concerned that
> adding the sync is not a robust fix and is possibly only working due
> to fortuitous timing.
Possibly -- but the only problem on the rare occasions where the timing
is not fortuitous is a spurious interrupt; the only reason the sync
needs to be there at all is to avoid the overhead of the extra interrupt
(and to avoid user complaints that they're getting "BAD" interrupts).
Note that many/most interrupt controller drivers don't even do that
much; they just have more fortuitous timing than the QE (and/or the
spurious interrupt is non-cascaded, and thus gets caught in
handle_level_irq and doesn't increment the spurious interrupt count).
-Scott
next prev parent reply other threads:[~2006-10-23 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 18:03 [PATCH] qe_ic: Do a sync when masking interrupts 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 [this message]
2006-10-23 15:29 ` Scott Wood
2006-10-23 17:52 ` Kumar Gala
2006-10-23 18:22 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 15:30 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
2006-10-25 4:47 ` Liu Dave-r63238
2006-10-23 18:53 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=453CDD70.9010100@freescale.com \
--to=scottwood@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 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).