From: Andrew Morton <akpm@osdl.org>
To: tglx@linutronix.de
Cc: torvalds@osdl.org, mingo@elte.hu, rmk+lkml@arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: ARM dyntick cleanup
Date: Sun, 2 Jul 2006 17:35:27 -0700 [thread overview]
Message-ID: <20060702173527.cbdbf0e1.akpm@osdl.org> (raw)
In-Reply-To: <1151885928.24611.24.camel@localhost.localdomain>
On Mon, 03 Jul 2006 02:18:48 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:
> Linus: "The hacks in kernel/irq/handle.c are really horrid. REALLY
> horrid."
>
> They are indeed. Move the dyntick quirks to ARM where they belong.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> Index: linux-2.6.git/include/asm-arm/hw_irq.h
> ===================================================================
> --- linux-2.6.git.orig/include/asm-arm/hw_irq.h 2006-07-03 00:13:24.000000000 +0200
> +++ linux-2.6.git/include/asm-arm/hw_irq.h 2006-07-03 00:52:04.000000000 +0200
> @@ -6,4 +6,15 @@
>
> #include <asm/mach/irq.h>
>
> +#if defined(CONFIG_NO_IDLE_HZ)
> +# include <asm/dyntick.h>
> +# define handle_dynamic_tick(action) \
> + if (!(action->flags & SA_TIMER) && system_timer->dyn_tick) { \
> + write_seqlock(&xtime_lock); \
> + if (system_timer->dyn_tick->state & DYN_TICK_ENABLED) \
> + system_timer->dyn_tick->handler(irq, 0, regs); \
> + write_sequnlock(&xtime_lock); \
> + }
> +#endif
> +
> #endif
> Index: linux-2.6.git/include/linux/irq.h
> ===================================================================
> --- linux-2.6.git.orig/include/linux/irq.h 2006-07-03 00:13:24.000000000 +0200
> +++ linux-2.6.git/include/linux/irq.h 2006-07-03 00:49:01.000000000 +0200
> @@ -182,6 +182,10 @@ extern int setup_irq(unsigned int irq, s
>
> #ifdef CONFIG_GENERIC_HARDIRQS
>
> +#ifndef handle_dynamic_tick
> +# define handle_dynamic_tick(a) do { } while (0)
> +#endif
> +
> #ifdef CONFIG_SMP
> static inline void set_native_irq_info(int irq, cpumask_t mask)
> {
This is not exactly a thing of beauty either. It's much cleaner to use
__attribute__((weak)), but that will add an empty call-return to everyone's
interrupts.
The requirement "if you implement this then you must do so as a macro" is a
bit regrettable. The ARCH_HAS_HANDLE_DYNAMIC_TICK approach would eliminate
that requirement.
btw, is this, from include/linux/irq.h:
/*
* Please do not include this file in generic code. There is currently
* no requirement for any architecture to implement anything held
* within this file.
*
* Thanks. --rmk
*/
still true?
next prev parent reply other threads:[~2006-07-03 0:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 0:18 [PATCH] genirq: ARM dyntick cleanup Thomas Gleixner
2006-07-03 0:35 ` Andrew Morton [this message]
2006-07-03 6:29 ` Thomas Gleixner
2006-07-03 6:57 ` Ingo Molnar
2006-07-04 11:54 ` Christoph Hellwig
2006-07-04 12:22 ` Ingo Molnar
2006-07-05 8:35 ` Russell King
2006-07-08 18:53 ` Christoph Hellwig
2006-07-03 7:41 ` Russell King
2006-07-03 7:55 ` Andrew Morton
2006-07-03 9:03 ` Russell King
2006-07-03 9:12 ` Andrew Morton
2006-07-03 16:56 ` Linus Torvalds
2006-07-03 17:13 ` Linus Torvalds
2006-07-03 17:27 ` Arjan van de Ven
2006-07-05 23:24 ` Randy.Dunlap
2006-07-05 23:35 ` Andrew Morton
2006-07-05 23:50 ` Randy.Dunlap
2006-07-05 23:53 ` Linus Torvalds
2006-07-06 0:02 ` Randy.Dunlap
2006-07-06 6:47 ` Giacomo A. Catenazzi
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=20060702173527.cbdbf0e1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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