From: Ralf Baechle <ralf@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: [PATCH v2] MIPS: R10000: Split R10000 definitions from R12000 and up
Date: Tue, 31 Mar 2015 14:17:58 +0200 [thread overview]
Message-ID: <20150331121757.GD28951@linux-mips.org> (raw)
In-Reply-To: <54BFA0DF.8000104@gentoo.org>
On Wed, Jan 21, 2015 at 07:51:43AM -0500, Joshua Kinard wrote:
> up
> Content-Type: text/plain; charset=utf-8
>
> From: Joshua Kinard <kumba@gentoo.org>
>
> This patch splits the old R10000 definitions so that the R10000_LLSC_WAR can be
> disabled and -mno-fix-r10000 passed to CFLAGS for systems running R12000 CPUs
> and greater. This allows the kernel to build without branch-likely
> instructions, which are considered deprecated in current MIPS implementations.
> Only R10000 systems with R2.6 and lower CPUs require branch-likely to work
> around a known hardware errata item.
The kernel doesn't use -mfix-r10000 rsp. -mno-fix-r10000 or any code that
would rely on the default setting for this option. The kernel rather
opencodes all these atomic sequences in inline assembler.
Only platforms which are known to be equipped with R10000 v2.6 processors
enable R10000_LLSC_WAR and I've done so quite intentionally not just for
some CPU configuration but the entire platforms which at this time are IP27
and IP28.
Another mysterious question of course is why
arch/mips/include/asm/mach-pmcs-msp71xx/msp_regops.h caters for the case
where R10000_LLSC_WAR is enabled. It won't be for that platform.
Ralf
next prev parent reply other threads:[~2015-03-31 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 12:51 [PATCH v2] MIPS: R10000: Split R10000 definitions from R12000 and up Joshua Kinard
2015-03-31 12:17 ` Ralf Baechle [this message]
2015-04-01 4:36 ` Joshua Kinard
2015-04-01 9:59 ` Tom Bogendoerfer
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=20150331121757.GD28951@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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 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.