[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1163969383.5826.123.camel@localhost.localdomain>
Date: Mon, 20 Nov 2006 07:49:42 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Sergei Shtylyov <sshtylyov@...mvista.com>, linuxppc-dev@...abs.org,
linux-kernel@...r.kernel.org, dwalker@...sta.com
Subject: Re: [PATCH] 2.6.18-rt7: PowerPC: fix breakage in threaded fasteoi
type IRQ handlers
On Sun, 2006-11-19 at 21:23 +0100, Ingo Molnar wrote:
> * Benjamin Herrenschmidt <benh@...nel.crashing.org> wrote:
>
> > > dont worry, it's -rt only stuff.
> >
> > Still, I'm curious :-) Besides, there have been people talking about
> > having -rt work on ppc64 so ...
>
> ok :)
>
> > What do you need an ack() for on fasteoi ? On all fasteoi controllers
> > I have, ack is implicit by obtaining the vector number and all there
> > is is an eoi...
>
> it's a compatibility hack only. Threaded handlers are a different type
> of flow, but often the fasteoi handler is not changed to the threaded
> handler so i changed it to be a threaded handler too.
>
> threaded handlers need a mask() + an ack(), because that's the correct
> model to map them to kernel threads - threaded handlers can be delayed
> for a long time if something higher-prio is preempting them.
Well, the principle of controllers that do fasteoi is that all
interrupts of the same priority or below are masked until eoi happens...
so I still don't see why you need that...
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists