Re: [PATCH -v6 08/13] tracing: add IRQENTRY_EXIT section for MIPS

From: Wu Zhangjin
Date: Sun Nov 08 2009 - 22:31:31 EST


Hi,

On Mon, 2009-11-09 at 03:26 +0100, Frederic Weisbecker wrote:
> On Mon, Oct 26, 2009 at 11:13:25PM +0800, Wu Zhangjin wrote:
> > This patch add a new section for MIPS to record the block of the hardirq
> > handling for function graph tracer(print_graph_irq) via adding the
> > __irq_entry annotation to the the entrypoints of the hardirqs(the block
> > with irq_enter()...irq_exit()).
> >
> > Thanks goes to Steven & Frederic Weisbecker for their feedbacks.
> >
> > Signed-off-by: Wu Zhangjin <wuzhangjin@xxxxxxxxx>
> > +
> > +/*
> > + * do_IRQ handles all normal device IRQ's (the special
> > + * SMP cross-CPU interrupts have their own specific
> > + * handlers).
> > + */
> > +unsigned int __irq_entry do_IRQ(unsigned int irq)
> > +{
> > + irq_enter();
> > + __DO_IRQ_SMTC_HOOK(irq);
> > + generic_handle_irq(irq);
> > + irq_exit();
> > +
> > + return 1;
> > +}
>
>
>
> Nano-neat:
>
> Why is it returning a value, it doesn't seem needed (the macro
> version didn't)?
>

Will remove it later.

> Anyway, that looks good to me. I hope the changes from macro
> to function calls will be ack by the MIPS maintainers.
>

Hope Ralf give some feedbacks about it ;)

> Reviewed-by: Frederic Weisbecker <fweisbec@xxxxxxxxx>
>

Thanks!

BTW:

Who should I resend this patchset to? you or Steven? If this patchset
are okay, I will rebase it on the latest tracing/core branch of -tip and
send the latest version out, and hope you can apply it, otherwise, I
need to rebase it to the future mainline versions again and again ;) and
at least, I have tested all of them and their combinations on YeeLoong
netbook, they work well. of course, more testing report from the other
MIPS developers are welcome ;)

Regards,
Wu Zhangjin

--
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/