Re: [PATCH 3.18-rc3 v9 5/5] arm: smp: Handle ipi_cpu_backtrace() using FIQ (if available)
From: Tim Sander
Date: Mon Dec 01 2014 - 08:54:22 EST
Am Montag, 1. Dezember 2014, 10:38:32 schrieb Russell King - ARM Linux:
> On Mon, Dec 01, 2014 at 11:32:00AM +0100, Tim Sander wrote:
> > Hi Russel, Daniel
> > Am Freitag, 28. November 2014, 10:08:28 schrieb Russell King - ARM Linux:
> > > The two things are mutually exclusive. You can either have FIQ being
> > > used
> > > for debug purposes, where we decode the FIQ reason and call some
> > > function
> > > (which means that we will only service one FIQ at a time) or you can use
> > > it in exclusive mode (provided by fiq.c) where your handler has sole
> > > usage
> > > of the vector, and benefits from fast and immediate servicing of the
> > > event.
> > As far as i am aware, die CONFIG_FIQ symbol is not pulled by all ARM
> > platforms. Since there are ARM platforms which don't use this symbol but
> > the hardware is fully capable of handling FIQ requests i would expect,
> > that adding CONFIG_FIQ to a plattform, that this platform honors the
> > set_fiq_handler functionality.
> That whole paragraph doesn't make much sense to me.
> Look, in my mind it is very simple. If you are using CONFIG_FIQ on a
> SMP platform, your life will be very difficult. The FIQ code enabled
> by that symbol is not designed to be used on SMP systems, *period*.
Well the only extra thing you had to do is set up the FIQ registers on every
cpu, but i would not call that very difficult. Other than that i am not aware of
any problems that are not also present on a uniprocessor system. So i have a
hard time following your reasoning why SMP is different from UP in regard to
> If you decide to enable CONFIG_FIQ, and you use that code on a SMP
> platform, I'm going to say right now so it's totally clear: if you
> encounter a problem, I don't want to know about it. The code is not
> designed for use on that situation.
Even with using the FIQ on a Linux SMP system you have not heard from me
before, as i knew that this is not your problem (and that is not to say that
there where none!). The only interface Linux has been making available is
set_fiq_handler. So it was clear that the FIQ is its own domain otherwise
untouched by the kernel. Now the line gets blurried with the linux kernel
moving to use the FIQ. And with the descicions forthcoming its not only
grabbing land it also claims a previous public path for its own. So it doesn't
help that its planting some flowers along the way. So please be nice to the
And i really don't get it, that neither ARM nor the kernel community sees fast
interrupts as a worthwhile usecase. Unfortunatly the interrupt latencies with
Linux are at least a order of magnitude higher than the pure hardware even
with longer pipelines can deliver.
> Therefore, as far as I'm concerned, the two facilities are mututally
Well can't have the cake and eat it too.
> I had thought about whether the IPI FIQ should be disabled when a
> replacement FIQ handler is installed, I deem it not to be a use case
> that the mainline kernel needs to be concerned about.
That would be nice.
> > Yes, but if the FIQ handler is also used for IPI, set_fiq_handler gets IPI
> > interrupts (with the patch starting this thread)? So i think that the
> > patch
> > needs to look like:
> > --- a/arch/arm/kernel/traps.c
> > +++ b/arch/arm/kernel/traps.c
> > @@ -483,6 +483,9 @@ asmlinkage void __exception_irq_entry
> > handle_fiq_as_nmi(struct pt_regs *regs)
> > +#ifndef CONFIG_FIQ
> > #ifdef CONFIG_ARM_GIC
> > gic_handle_fiq_ipi();
> > #endif
> > +#endif
> No. With a single zImage kernel, you could very well have SMP and FIQ
> both enabled, but have a non-SMP platform using FIQ, but also support
> SMP platforms as well. Your change prevents that happening.
Ah, well i have to get used to this "new" devicetree thingy, where one size
Still if you boot a single process system which has FIQ available and has a
GIC with such a kernel, then you also reprogramm the IPI's as FIQs. But i
guess thats not a problem as Linux does not self IPI the kernel as other os'es
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/