From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
nickpiggin@yahoo.com.au,
Linux Arch list <linux-arch@vger.kernel.org>
Subject: Re: [patch] sched: unlocked context-switches
Date: Sat, 09 Apr 2005 19:22:23 +1000 [thread overview]
Message-ID: <1113038543.9568.430.camel@gaston> (raw)
In-Reply-To: <20050409043848.GA2677@elte.hu>
On Sat, 2005-04-09 at 06:38 +0200, Ingo Molnar wrote:
> * Luck, Tony <tony.luck@intel.com> wrote:
>
> > >tested on x86, and all other arches should work as well, but if an
> > >architecture has irqs-off assumptions in its switch_to() logic
> > >it might break. (I havent found any but there may such assumptions.)
> >
> > The ia64_switch_to() code includes a section that can change a pinned
> > MMU mapping (when the stack for the new process is in a different
> > granule from the stack for the old process). [...]
>
> thanks - updated patch below. Any other architectures that switch the
> kernel stack in a nonatomic way? x86/x64 switches it atomically.
ppc64 already has a local_irq_save/restore in switch_to, around the low
level asm bits, so it should be fine.
Ben.
next prev parent reply other threads:[~2005-04-09 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 18:38 [patch] sched: unlocked context-switches 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 [this message]
2005-04-09 22:46 ` David S. Miller
2005-04-10 7:23 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 12:16 Ingo Molnar
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=1113038543.9568.430.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox