From: Richard Henderson <rth@twiddle.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
mingo@elte.hu, tony.luck@intel.com, linux-kernel@vger.kernel.org,
akpm@osdl.org, nickpiggin@yahoo.com.au,
linux-arch@vger.kernel.org
Subject: Re: [patch] sched: unlocked context-switches
Date: Sun, 10 Apr 2005 00:23:57 -0700 [thread overview]
Message-ID: <20050410072357.GA2155@twiddle.net> (raw)
In-Reply-To: <20050409154612.55d6a6fa.davem@davemloft.net>
On Sat, Apr 09, 2005 at 03:46:12PM -0700, David S. Miller wrote:
> On Sat, 09 Apr 2005 19:22:23 +1000
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > ppc64 already has a local_irq_save/restore in switch_to, around the low
> > level asm bits, so it should be fine.
>
> Sparc64 essentially does as well. In fact, it uses an IRQ disable
> which is stronger than local_irq_save in that it disables reception
> of CPU cross-calls as well.
Alpha does the switch in PALmode, which is never interruptable.
r~
next prev parent reply other threads:[~2005-04-10 7:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 18:38 [patch] sched: unlocked context-switches Luck, Tony
2005-04-08 18:38 ` Luck, Tony
2005-04-09 4:38 ` Ingo Molnar
2005-04-09 6:28 ` Nick Piggin
2005-04-09 6:55 ` Ingo Molnar
2005-04-09 7:11 ` Nick Piggin
2005-04-09 9:22 ` Benjamin Herrenschmidt
2005-04-09 22:46 ` David S. Miller
2005-04-10 7:23 ` Richard Henderson [this message]
[not found] <3R6Ir-89Y-23@gated-at.bofh.it>
2005-04-09 6:32 ` David Mosberger-Tang
2005-04-09 7:07 ` Ingo Molnar
2005-04-09 7:15 ` David Mosberger
2005-04-09 22:58 ` David S. Miller
2005-04-10 6:43 ` Ingo Molnar
2005-04-12 1:06 ` David Mosberger
2005-04-12 2:12 ` Nick Piggin
2005-04-12 17:14 ` David Mosberger
2005-04-13 3:26 ` Nick Piggin
2005-04-12 6:42 ` Ingo Molnar
2005-04-12 17:15 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 12:16 Ingo Molnar
2005-04-29 9:09 ` Andrew Morton
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=20050410072357.GA2155@twiddle.net \
--to=rth@twiddle.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.