From: David Gibson <david@gibson.dropbear.id.au>
To: Valentine Barshak <vbarshak@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [ PATCH ] PowerPC cascade UIC IRQ handler fix.
Date: Tue, 14 Aug 2007 11:35:10 +1000 [thread overview]
Message-ID: <20070814013510.GA31123@localhost.localdomain> (raw)
In-Reply-To: <46C04F07.3040909@ru.mvista.com>
On Mon, Aug 13, 2007 at 04:31:03PM +0400, Valentine Barshak wrote:
[snip]
> >> Ok, here's a patch which fixes up the flow handling on the UIC. It
> >> needs some polish yet, but should be ok to test. Valentine, can you
> >> test this on your setup, *without* your original proposed patch.
> >> Eventually, for robustness, we'll want something like your original
> >> patch as well for robustness, but in the meantime leaving it out
> >> should tell us if my patch is actually having the intended effect.
> >
> > Valentine, it would be really helpful if you could test this on the
> > problem you observed with the cascade interrupt. Any word on this?
> >
>
> Thanks David,
> the patch works fine here (without the original one).
Ok, great.
> Don't think we really need a "fastcall" here on a powerpc though.
Oh, yeah, that's just copied from the generic handle_level_irq().
> The original patch also fixes a minor issue with /proc/interrupts
> (the the "if (trigger)" stuff).
> Currently level-triggered interrupts are displayed as edge-triggered
> ones and vice versa.
Yes, we'll still want two patches similar to your original: one to fix
the cosmetic /proc/interrupts problem, the other to make the cascade
handler more robust against spurious interrupts. I just wanted to see
if this flow handler change fixed the basic problem.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2007-08-14 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 16:35 [ PATCH ] PowerPC cascade UIC IRQ handler fix Valentine Barshak
2007-08-02 3:48 ` David Gibson
2007-08-02 20:08 ` Josh Boyer
2007-08-03 11:09 ` Valentine Barshak
2007-08-03 1:18 ` Benjamin Herrenschmidt
2007-08-03 4:57 ` David Gibson
2007-08-03 6:23 ` David Gibson
2007-08-13 1:08 ` David Gibson
2007-08-13 12:31 ` Valentine Barshak
2007-08-14 1:35 ` David Gibson [this message]
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=20070814013510.GA31123@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=vbarshak@ru.mvista.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 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).