From: David Daney <ddaney@caviumnetworks.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Define __arch_swab64 for all mips r2 cpus (v2).
Date: Tue, 30 Jun 2009 18:13:41 -0700 [thread overview]
Message-ID: <4A4AB845.1030906@caviumnetworks.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0907010132500.23134@eddie.linux-mips.org>
Maciej W. Rozycki wrote:
> On Mon, 29 Jun 2009, Ralf Baechle wrote:
>
>>> Some CPUs implement mipsr2, but because they are a super-set of
>>> mips64r2 do not define CONFIG_CPU_MIPS64_R2. Cavium OCTEON falls into
>>> this category. We would still like to use the optimized
>>> implementation, so since we have already checked for
>>> CONFIG_CPU_MIPSR2, checking for CONFIG_64BIT instead of
>>> CONFIG_CPU_MIPS64_R2 is sufficient.
>>>
>>> Change from v1: Add comments about why the change is safe.
>> Thanks, applied. Though this sort of patch make me thing that maybe we
>> rather should have treated the cnMIPS cores differently.
>
> This is a pure code generation option and it asks for "select
> CPU_MIPS64_R2" under CPU_OCTEON (or whatever option is used for that
> chip). Or something like "select ISA_MIPS64_R2" actually, as we want to
> keep CPU_foo as the -march=, etc. designator. IOW it looks like we lack
> ISA supersetting along the lines of how tools handle it.
>
The problem with CPU_MIPS64_R2 in the kernel is that it means two
unrelated things:
1) The cpu can execute all mips64r2 ISA instructions.
2) The cpu requires that all worse case cache and execution hazards are
handled.
In the case of the Octeon processors, #1 is true, but we can get better
performance by omitting many of the hazard barriers because they are
unneeded.
David Daney
next prev parent reply other threads:[~2009-07-01 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 16:54 [PATCH] MIPS: Define __arch_swab64 for all mips r2 cpus (v2) David Daney
2009-06-29 19:34 ` Ralf Baechle
2009-07-01 0:37 ` Maciej W. Rozycki
2009-07-01 1:13 ` David Daney [this message]
2009-07-01 1:36 ` Maciej W. Rozycki
2009-07-01 18:40 ` Ralf Baechle
2009-07-01 18:20 ` Ralf Baechle
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=4A4AB845.1030906@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox