Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: LMO <linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH v2] Alchemy: cpu feature override constants.
Date: Wed, 26 Nov 2008 15:48:21 +0300	[thread overview]
Message-ID: <492D4595.7060903@ru.mvista.com> (raw)
In-Reply-To: <20081125231230.GA10366@roarinelk.homelinux.net>

Hello.

Manuel Lauss wrote:

> Add cpu feature override constants for Alchemy.
>
> This helps code generation: fls() for instance is compiled without
> using the clz instruction; other macros which do runtime feature
> detection fall back on safe legacy code as well.  Adding this override
> fixes that.  As a sideeffect, the size of a kernel built with an
> extended db1200 defconfig is reduced by over 200kB:
>
>    text    data     bss     dec     hex filename
> 3901089  124160  436528 4461777  4414d1 vmlinux
> 3676433  124096  436528 4237057  40a701 vmlinux-patched
>   

   Great!

> Signed-off-by: Manuel Lauss <mano@roarinelk.homelinux.net>
>   

   The whitespace police on the road. :-)

> diff --git a/arch/mips/include/asm/mach-au1x00/cpu-feature-overrides.h b/arch/mips/include/asm/mach-au1x00/cpu-feature-overrides.h
> new file mode 100644
> index 0000000..c22492e
> --- /dev/null
> +++ b/arch/mips/include/asm/mach-au1x00/cpu-feature-overrides.h
> @@ -0,0 +1,51 @@
>   
[...]
> +
> +#define cpu_dcache_line_size()	32
> +#define cpu_icache_line_size()  32
>   

   Inconsistent alignment.

WBR, Sergei

      parent reply	other threads:[~2008-11-26 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 23:12 [PATCH v2] Alchemy: cpu feature override constants Manuel Lauss
2008-11-25 23:23 ` David Daney
2008-11-26  5:50   ` Manuel Lauss
2008-11-26  7:51     ` Ralf Baechle
2008-11-26  8:08       ` Manuel Lauss
2008-11-26  8:34         ` Ralf Baechle
2008-11-26 12:48 ` Sergei Shtylyov [this message]

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=492D4595.7060903@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    --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