[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201012103021.GC7765@alpha.franken.de>
Date: Mon, 12 Oct 2020 12:30:21 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] MIPS: cpu-probe: introduce exclusive R3k CPU probe
On Thu, Oct 08, 2020 at 11:33:26PM +0200, Thomas Bogendoerfer wrote:
> Running a kernel on a R3k of machine definitly will never see one of
> the newer CPU cores. And since R3k system usually are low on memory
> we could save quite some kbytes:
>
> text data bss dec hex filename
> 15070 88 32 15190 3b56 arch/mips/kernel/cpu-probe.o
> 844 4 16 864 360 arch/mips/kernel/cpu-r3k-probe.o
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
> ---
> arch/mips/kernel/Makefile | 8 +-
> arch/mips/kernel/cpu-r3k-probe.c | 171 +++++++++++++++++++++++++++++++++++++++
> 2 files changed, 178 insertions(+), 1 deletion(-)
> create mode 100644 arch/mips/kernel/cpu-r3k-probe.c
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists