linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tglx@linutronix.de
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, akpm@linux-foundation.org,
	mingo@elte.hu, peterz@infradead.org, alan@lxorguk.ukuu.org.uk,
	andi@firstfloor.org, gregkh@suse.de, acme@redhat.com
Subject: Re: [patch 0/2] Run interrupt handlers always with interrupts disabled
Date: Thu, 25 Mar 2010 20:34:14 -0700 (PDT)	[thread overview]
Message-ID: <20100325.203414.149691680.davem@davemloft.net> (raw)
In-Reply-To: <20100326000325.917127328@linutronix.de>

From: Thomas Gleixner <tglx@linutronix.de>
Date: Fri, 26 Mar 2010 00:06:44 -0000

> The following patch series removes the IRQF_DISABLED functionality
> from the core interrupt code and runs all interrupt handlers with
> interrupts disabled.
> 
> IRQF_DISABLED is kept as a define and scheduled for feature removal.
> 
> I booted and stressed that patches w/o any obvious fallout on more
> than 20 different systems in my arsenal of test machines which
> includes various embedded non x86 systems.
> 
> To debug eventual latency issues we (admittedly I talked acme into
> looking at that) want to extend perf with a top like tool to monitor
> the maximum runtime of interrupt handlers with the already existing
> tracepoints.

Acked-by: David S. Miller <davem@davemloft.net>

  parent reply	other threads:[~2010-03-26  3:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  0:06 [patch 0/2] Run interrupt handlers always with interrupts disabled Thomas Gleixner
2010-03-26  0:06 ` [patch 1/2] genirq: Run irq handlers " Thomas Gleixner
2010-03-26  6:13   ` Andi Kleen
2010-03-26 13:05     ` Thomas Gleixner
2010-03-30  5:33       ` Andi Kleen
2010-03-31 11:16         ` Thomas Gleixner
2010-04-02  9:31           ` Pavel Machek
2010-04-02 20:42             ` Thomas Gleixner
2010-04-02 21:09               ` Pavel Machek
2010-04-02 21:31                 ` Peter Zijlstra
2010-04-02 22:51                 ` Thomas Gleixner
2010-04-03  4:45                   ` Pavel Machek
2010-04-03  4:45                     ` Pavel Machek
2010-05-25 20:32   ` Venkatesh Pallipadi
2010-03-26  0:06 ` [patch 2/2] genirq: Remove IRQF_DISABLED from core code Thomas Gleixner
2010-03-26  0:06   ` Thomas Gleixner
2010-03-26  6:20   ` Andi Kleen
2010-03-26 11:19     ` Thomas Gleixner
2010-03-26 11:19       ` Thomas Gleixner
2010-03-26  3:34 ` David Miller [this message]
2010-03-26  8:14 ` [patch 0/2] Run interrupt handlers always with interrupts disabled Russell King
2010-03-26  8:14   ` Russell King
2010-03-26  9:20   ` Ingo Molnar
2010-03-26  9:20     ` Ingo Molnar
2010-03-26  9:28     ` Peter Zijlstra
2010-03-26 12:02       ` Jamie Lokier
2010-03-26  9:59     ` Alan Cox
2010-03-26 10:08       ` Peter Zijlstra
2010-03-26 10:12         ` Andi Kleen
2010-03-26 10:53         ` Ingo Molnar
2010-03-26 12:00         ` Nicolas Pitre
2010-03-26 12:06           ` Jamie Lokier

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=20100325.203414.149691680.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=gregkh@suse.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).