linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Babu Moger <babu.moger@oracle.com>
To: davem@davemloft.net, peterz@infradead.org, mingo@redhat.com,
	arnd@arndb.de
Cc: babu.moger@oracle.com, shannon.nelson@oracle.com,
	haakon.bugge@oracle.com, steven.sistare@oracle.com,
	vijay.ac.kumar@oracle.com, jane.chu@oracle.com,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: [PATCH v3 3/7] arch/sparc: Define config parameter CPU_BIG_ENDIAN
Date: Tue, 23 May 2017 15:45:54 -0600	[thread overview]
Message-ID: <1495575958-1022566-4-git-send-email-babu.moger@oracle.com> (raw)
In-Reply-To: <1495575958-1022566-1-git-send-email-babu.moger@oracle.com>

Found this problem while enabling queued rwlock on SPARC.
The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the
specific byte in qrwlock structure. Without this parameter,
we clear the wrong byte. Here is the code.

static inline u8 *__qrwlock_write_byte(struct qrwlock *lock)
 {
	return (u8 *)lock + 3 * IS_BUILTIN(CONFIG_CPU_BIG_ENDIAN);
 }

Define CPU_BIG_ENDIAN for SPARC to fix it.

Signed-off-by: Babu Moger <babu.moger@oracle.com>
Reviewed-by: Håkon Bugge <haakon.bugge@oracle.com>
Reviewed-by: Jane Chu <jane.chu@oracle.com>
Reviewed-by: Shannon Nelson <shannon.nelson@oracle.com>
Reviewed-by: Vijay Kumar <vijay.ac.kumar@oracle.com>
---
 arch/sparc/Kconfig |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
index 908f019..2f58c16 100644
--- a/arch/sparc/Kconfig
+++ b/arch/sparc/Kconfig
@@ -92,6 +92,10 @@ config ARCH_DEFCONFIG
 config ARCH_PROC_KCORE_TEXT
 	def_bool y
 
+config CPU_BIG_ENDIAN
+	bool
+	default y if SPARC
+
 config ARCH_ATU
 	bool
 	default y if SPARC64
-- 
1.7.1


  parent reply	other threads:[~2017-05-23 21:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 21:45 [PATCH v3 0/7] Enable queued rwlock and queued spinlock for SPARC Babu Moger
2017-05-23 21:45 ` Babu Moger
2017-05-23 21:45 ` [PATCH v3 1/7] arch/sparc: Remove the check #ifndef __LINUX_SPINLOCK_TYPES_H Babu Moger
2017-05-23 21:45   ` Babu Moger
2017-05-23 21:45 ` [PATCH v3 2/7] kernel/locking: Fix compile error with qrwlock.c Babu Moger
2017-05-23 21:45   ` Babu Moger
2017-05-23 21:45 ` Babu Moger [this message]
2017-05-23 21:45   ` [PATCH v3 3/7] arch/sparc: Define config parameter CPU_BIG_ENDIAN Babu Moger
2017-05-24  9:48   ` Geert Uytterhoeven
2017-05-24  9:48     ` Geert Uytterhoeven
2017-05-24 14:37     ` Babu Moger
2017-05-23 21:45 ` [PATCH v3 4/7] arch/sparc: Introduce cmpxchg_u8 SPARC Babu Moger
2017-05-23 21:45   ` Babu Moger
2017-05-23 21:45 ` [PATCH v3 5/7] arch/sparc: Enable queued rwlocks for SPARC Babu Moger
2017-05-23 21:45 ` [PATCH v3 6/7] arch/sparc: Introduce xchg16 " Babu Moger
2017-05-23 21:45   ` Babu Moger
2017-05-23 21:45 ` [PATCH v3 7/7] arch/sparc: Enable queued spinlock support " Babu Moger
2017-05-23 21:45   ` Babu Moger

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=1495575958-1022566-4-git-send-email-babu.moger@oracle.com \
    --to=babu.moger@oracle.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=haakon.bugge@oracle.com \
    --cc=jane.chu@oracle.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=shannon.nelson@oracle.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=steven.sistare@oracle.com \
    --cc=vijay.ac.kumar@oracle.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;
as well as URLs for NNTP newsgroup(s).