public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] irq: remove IRQF_DISABLED
Date: Mon, 02 Mar 2009 19:02:55 +0100	[thread overview]
Message-ID: <1236016975.5330.990.camel@laptop> (raw)
In-Reply-To: <200903021855.02765.bzolnier@gmail.com>

On Mon, 2009-03-02 at 18:55 +0100, Bartlomiej Zolnierkiewicz wrote:
> IDE IRQ handler (& probably many others) assume that IRQ layer won't be
> trying to call it again while IRQ is being serviced -- is this going to
> change with the introduction of threaded IRQs?

No, the real hardirq handler needs to disable the irq line before
telling it wants the thread to run. The thread will then have to
re-enable the irq line after its done.

  reply	other threads:[~2009-03-02 18:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 12:21 [RFC][PATCH] irq: remove IRQF_DISABLED Peter Zijlstra
2009-03-02 14:43 ` Ingo Molnar
2009-03-02 15:47   ` Matthew Wilcox
2009-03-02 15:59     ` Peter Zijlstra
2009-03-02 16:32       ` Matthew Wilcox
2009-03-02 21:01       ` Russell King
2009-03-02 21:17         ` Ingo Molnar
2009-03-02 21:17           ` Ingo Molnar
2009-03-02 17:11 ` Linus Torvalds
2009-03-02 17:55   ` Bartlomiej Zolnierkiewicz
2009-03-02 18:02     ` Peter Zijlstra [this message]
2009-03-02 18:07     ` Peter Zijlstra
2009-03-02 18:27       ` Bartlomiej Zolnierkiewicz
2009-03-02 18:29     ` Linus Torvalds
2009-03-02 18:48       ` Bartlomiej Zolnierkiewicz
2009-03-02 19:06         ` Linus Torvalds
2009-03-02 19:18           ` Bartlomiej Zolnierkiewicz
2009-03-02 17:56   ` Peter Zijlstra
2009-03-02 18:45   ` Vadim Lobanov
2009-03-02 18:45     ` Vadim Lobanov
2009-03-02 18:54     ` Linus Torvalds
2009-03-05 15:40       ` Mark Lord
2009-03-02 21:17   ` Alan Cox
2009-03-02 21:17     ` Alan Cox
2009-03-06  8:58   ` Benjamin Herrenschmidt
2009-03-06  9:12     ` Peter Zijlstra
2009-03-06  9:59       ` Benjamin Herrenschmidt
2009-03-06 10:05         ` Benjamin Herrenschmidt
2009-03-06 10:24         ` Peter Zijlstra
2009-03-06 17:02           ` Peter Zijlstra
2009-03-06 21:40             ` Benjamin Herrenschmidt
2009-03-02 17:55 ` Andrew Morton
2009-03-02 18:10   ` Peter Zijlstra

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=1236016975.5330.990.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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