From: Peter Zijlstra <peterz@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [RFC][PATCH] sparc64: remove __ARCH_WANT_UNLOCKED_CTXSW usage
Date: Thu, 22 Dec 2011 20:16:39 +0100 [thread overview]
Message-ID: <1324581399.24803.38.camel@twins> (raw)
In-Reply-To: <20111221.180549.2295489434558987482.davem@davemloft.net>
On Wed, 2011-12-21 at 18:05 -0500, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Wed, 21 Dec 2011 16:44:26 -0500 (EST)
>
> > From: Peter Zijlstra <peterz@infradead.org>
> > Date: Mon, 12 Dec 2011 16:14:12 +0100
> >
> >> The only thing resting me is asking you to simply test the below patch
> >> and report what happens. Hopefully things will simply work.. if not I've
> >> messed up and need to go look harder :/
> >
> > I'll give it a spin, and get back to you, thanks!
>
> Ok, so far so good, I stressed out my Niagara-T3 box for a while doing gcc
> bootstraps, running the testsuite, etc. and all seems well so far.
>
> I'll keep beating on it and let you know if anything funny happens, but for
> now as far as I'm concerned:
>
> Acked-by: David S. Miller <davem@davemloft.net>
Thanks David!!
I'll probably post again (and propose merger) once Catalin's patches
that remove __ARCH_WANT_INTERRUPTS_ON_CTXSW from ARM have landed.
ARM being the last user of that feature, and with only SPARC64 and IA64
(needlessly) using __ARCH_WANT_UNLOCKED_CTXSW we could finally remove
some of that hairy code from the core scheduler.
next prev parent reply other threads:[~2011-12-22 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 15:14 Peter Zijlstra
2011-12-21 21:44 ` David Miller
2011-12-21 23:05 ` David Miller
2011-12-22 19:16 ` Peter Zijlstra [this message]
2011-12-22 19:22 ` David Miller
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=1324581399.24803.38.camel@twins \
--to=peterz@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sparclinux@vger.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
all inboxes | Powered by JetHome®