From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: kosaki.motohiro@jp.fujitsu.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Limit irq nesting
Date: Thu, 17 Jul 2008 10:57:56 +0900 [thread overview]
Message-ID: <20080717105532.157E.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807162128060.24301@devserv.devel.redhat.com>
Hi Mikulas,
> ---
> include/linux/interrupt.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.26-rc8/include/linux/interrupt.h
> ===================================================================
> --- linux-2.6.26-rc8.orig/include/linux/interrupt.h 2008-06-25 03:58:20.000000000 +0200
> +++ linux-2.6.26-rc8/include/linux/interrupt.h 2008-07-01 17:42:44.000000000 +0200
> @@ -16,6 +16,11 @@
> #include <asm/system.h>
>
> /*
> + * Max number of interrupt handlers on a stack. To prevent stack overflow.
> + */
> +#define MAX_NESTED_INTERRUPTS 2
> +
> +/*
> * These correspond to the IORESOURCE_IRQ_* defines in
> * linux/ioport.h to select the interrupt line behaviour. When
> * requesting an interrupt without specifying a IRQF_TRIGGER, the
I have no objection to your approach.
but I don't know MAX_NESTED_INTERRUPTS is properly or not.
Could you explain why MAX_NESTED_INTERRUPTS is two?
Is it architecture independent properly number?
> @@ -95,7 +100,7 @@ extern void devm_free_irq(struct device
> #ifdef CONFIG_LOCKDEP
> # define local_irq_enable_in_hardirq() do { } while (0)
> #else
> -# define local_irq_enable_in_hardirq() local_irq_enable()
> +# define local_irq_enable_in_hardirq() do { if (hardirq_count() < (MAX_NESTED_INTERRUPTS << HARDIRQ_SHIFT)) local_irq_enable(); } while (0)
> #endif
>
> extern void disable_irq_nosync(unsigned int irq);
next prev parent reply other threads:[~2008-07-17 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 1:42 Mikulas Patocka
2008-07-17 1:57 ` KOSAKI Motohiro [this message]
2008-07-17 11:59 ` Mikulas Patocka
-- strict thread matches above, loose matches on Subject: below --
2008-06-24 5:54 [10 PATCHES] inline functions to avoid stack overflow Mikulas Patocka
2008-06-24 6:06 ` [PATCH] limit irq nesting Mikulas Patocka
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=20080717105532.157E.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®