From: Peter Zijlstra <peterz@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Davidlohr Bueso <davidlohr@hp.com>,
Ingo Molnar <mingo@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Jason Low <jason.low2@hp.com>, Waiman Long <waiman.long@hp.com>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
John David Anglin <dave.anglin@bell.net>,
"Chandramouleeswaran, Aswin" <aswin@hp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>,
David Miller <davem@davemloft.net>,
James Hogan <james.hogan@imgtec.com>,
Chris Metcalf <cmetcalf@tilera.com>,
Vineet Gupta <vgupta@synopsys.com>
Subject: Re: [PATCH 2/2] locking/rwsem: Disable optimistic spinning for PA-RISC
Date: Fri, 6 Jun 2014 20:01:02 +0200 [thread overview]
Message-ID: <20140606180102.GY13930@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <1402077427.2207.91.camel@dabdike.int.hansenpartnership.com>
On Fri, Jun 06, 2014 at 10:57:07AM -0700, James Bottomley wrote:
> > diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
> > index 29f2e988c56a..407c87d9879a 100644
> > --- a/arch/sparc/Kconfig
> > +++ b/arch/sparc/Kconfig
> > @@ -78,6 +78,7 @@ config SPARC64
^^^^^^^^^^^^^^
> > select HAVE_C_RECORDMCOUNT
> > select NO_BOOTMEM
> > select HAVE_ARCH_AUDITSYSCALL
> > + select ARCH_SUPPORTS_ATOMIC_RMW
>
> Sparc64 does, Sparc32 doesn't, so shouldn't that be
>
> select ARCH_SUPPORTS_ATOMIC_RMW if 64BIT
>
> ?
arch/sparc/Kconfig has 3 large sections:
config SPARC (included in both)
config SPARC32 (specific to 32bit)
config SPARC64 (specific to 64bit)
I added it to the last.
next prev parent reply other threads:[~2014-06-06 18:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 15:55 [PATCH 0/2] locking/rwsem: disable optimistic spinning for PA-RISC Davidlohr Bueso
2014-06-06 15:55 ` [PATCH 1/2] locking/rwsem: Add CONFIG_RWSEM_SPIN_ON_OWNER Davidlohr Bueso
2014-06-06 17:13 ` Jason Low
2014-06-06 18:12 ` Davidlohr Bueso
2014-06-06 18:48 ` Davidlohr Bueso
2014-06-06 19:08 ` Jason Low
2014-06-06 19:20 ` Davidlohr Bueso
2014-06-06 15:55 ` [PATCH 2/2] locking/rwsem: Disable optimistic spinning for PA-RISC Davidlohr Bueso
2014-06-06 16:09 ` James Bottomley
2014-06-06 17:11 ` Peter Zijlstra
2014-06-06 17:19 ` Chris Metcalf
2014-06-06 17:22 ` Linus Torvalds
2014-06-06 17:53 ` Peter Zijlstra
2014-06-06 17:57 ` James Bottomley
2014-06-06 17:58 ` James Bottomley
2014-06-06 18:01 ` Peter Zijlstra [this message]
2014-07-16 19:24 ` [tip:locking/urgent] locking/mutex: Disable optimistic spinning on some architectures tip-bot for Peter Zijlstra
2014-07-17 11:51 ` Christian Borntraeger
2014-07-17 11:58 ` Christian Borntraeger
2014-07-18 3:07 ` Davidlohr Bueso
2014-07-18 3:10 ` Davidlohr Bueso
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=20140606180102.GY13930@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aswin@hp.com \
--cc=cmetcalf@tilera.com \
--cc=dave.anglin@bell.net \
--cc=davem@davemloft.net \
--cc=davidlohr@hp.com \
--cc=james.hogan@imgtec.com \
--cc=jason.low2@hp.com \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@synopsys.com \
--cc=waiman.long@hp.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.