linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	Matthew Wilcox <matthew@wil.cx>, Yinghai Lu <yinghai@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rabin Vincent <rabin@rab.in>, lkml <linux-kernel@vger.kernel.org>,
	penberg@cs.helsinki.fi,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-arch@vger.kernel.org
Subject: Re: start_kernel(): bug: interrupts were enabled early
Date: Wed, 31 Mar 2010 23:30:40 +0100	[thread overview]
Message-ID: <20100331223039.GA8999@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4BB3C540.9000405@zytor.com>

On Wed, Mar 31, 2010 at 02:57:20PM -0700, H. Peter Anvin wrote:
> On 03/31/2010 02:54 PM, Russell King wrote:
> > On Wed, Mar 31, 2010 at 04:42:25PM -0500, Christoph Lameter wrote:
> >> Do not run the checks while we are in a single threaded context?
> >>
> >> I thought we had some dynamic code patching thingamy that could change
> >> those when we go to smp mode?
> > 
> > You have to remember that on embedded architectures, such as ARM,
> > where XIP is supported we can't change the text segment at run time -
> > which means dynamic code patching won't work.
> > 
> > However, the kernel should still work in such situations.
> > 
> 
> The question still remains what the incremental cost is of doing
> irqsave/irqrestore.

Compared to irq disable/enable, it wouldn't be much higher; saving
can be done by a direct register to register move, so that should be
relatively cheap.  The restore may be a little bit more depending on
the CPU arch version, but not significant.

So there shouldn't be a problem from ARM POV to switch to using
irqsave/irqrestore.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2010-03-31 22:32 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 19:41 start_kernel(): bug: interrupts were enabled early Rabin Vincent
2010-03-31 20:40 ` Andrew Morton
2010-03-31 20:47   ` Yinghai Lu
2010-03-31 20:52     ` Andrew Morton
2010-03-31 21:12       ` H. Peter Anvin
2010-03-31 21:28         ` Andrew Morton
2010-03-31 22:35           ` Benjamin Herrenschmidt
2010-04-01 16:13         ` Linus Torvalds
2010-04-01 14:27           ` Andrew Morton
2010-04-01 20:12             ` Linus Torvalds
2010-04-02 14:46             ` David Howells
2010-04-02 14:54               ` Linus Torvalds
2010-04-07 19:09           ` Kevin Hilman
2010-04-08 15:55             ` Américo Wang
2010-03-31 21:01     ` Matthew Wilcox
2010-03-31 21:05       ` H. Peter Anvin
2010-03-31 21:17         ` Matthew Wilcox
2010-03-31 21:42           ` Christoph Lameter
2010-03-31 21:54             ` Russell King
2010-03-31 21:57               ` H. Peter Anvin
2010-03-31 22:30                 ` Russell King [this message]
2010-03-31 22:37                 ` Benjamin Herrenschmidt
2010-03-31 22:49                   ` Andrew Morton
2010-04-01  1:17                     ` Benjamin Herrenschmidt
2010-03-31 22:26                       ` Andrew Morton
2010-04-01  6:26                         ` H. Peter Anvin
2010-04-01  3:33                           ` Andrew Morton
2010-04-01  6:48                             ` Benjamin Herrenschmidt
2010-04-01 16:15                               ` H. Peter Anvin
2010-04-01 11:06                             ` David Howells
2010-04-01 15:55                               ` Christoph Lameter
2010-04-01 23:00                               ` Benjamin Herrenschmidt
2010-04-01  6:50                           ` Benjamin Herrenschmidt
2010-03-31 22:36             ` Benjamin Herrenschmidt
2010-04-01 15:57               ` Christoph Lameter
2010-03-31 21:05     ` Russell King
2010-03-31 21:08       ` H. Peter Anvin
2010-03-31 22:31     ` Benjamin Herrenschmidt
2010-03-31 22:36       ` H. Peter Anvin
2010-03-31 22:58     ` David Howells
2010-04-01  9:41       ` Jamie Lokier
2010-04-01 11:23         ` Matthew Wilcox
2010-04-01 10:50       ` David Howells

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=20100331223039.GA8999@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=cl@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=penberg@cs.helsinki.fi \
    --cc=rabin@rab.in \
    --cc=yinghai@kernel.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).