public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: kaos@sgi.com, akpm@osdl.org, zwane@linuxpower.ca, ak@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6] Allow x86_64 to reenable interrupts on contention
Date: Tue, 27 Jul 2004 19:24:54 -0700	[thread overview]
Message-ID: <20040727192454.787c6b62.davem@redhat.com> (raw)
In-Reply-To: <20040728022131.GL2334@holomorphy.com>

On Tue, 27 Jul 2004 19:21:31 -0700
William Lee Irwin III <wli@holomorphy.com> wrote:

> and may also have issues with
> architectures (e.g. sparc/sparc64) which need the interrupt disablement
> in e.g. spin_lock_irqsave() to be done in the same call frame as the
> spin_unlock_irqrestore() etc.

This only was a problem on sparc, and it no longer exists at all
in 2.6.x kernels.  It was too much of a pain to keep teaching
people that violated this, and it resulted in some contorted
code as well.

So don't worry about this at all in 2.6.x and later.

  reply	other threads:[~2004-07-28  2:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  9:29 [PATCH][2.6] Allow x86_64 to reenable interrupts on contention Zwane Mwaikambo
2004-07-27 11:26 ` Andi Kleen
2004-07-27 14:31   ` Zwane Mwaikambo
2004-07-27 15:37     ` Andi Kleen
2004-07-27 16:36       ` Ricky Beam
2004-07-28  8:47         ` Paul Jackson
2004-07-28  1:38       ` Zwane Mwaikambo
2004-07-27 19:01     ` Andrew Morton
2004-07-28  0:14       ` William Lee Irwin III
2004-07-28  0:35         ` Keith Owens
2004-07-28  0:40           ` William Lee Irwin III
2004-07-28  1:48             ` Keith Owens
2004-07-28  2:21               ` William Lee Irwin III
2004-07-28  2:24                 ` David S. Miller [this message]
2004-07-28  8:20                   ` William Lee Irwin III
2004-07-28  1:30           ` Zwane Mwaikambo

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=20040727192454.787c6b62.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=kaos@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    --cc=zwane@linuxpower.ca \
    /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