From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: sparclinux@vger.kernel.org
Subject: [PATCH] sparc32: max_cache_size fallback
Date: Sat, 12 Aug 2006 19:14:44 +0000 [thread overview]
Message-ID: <44de28a4e7531@wp.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
From: Krzysztof Helt (krzysztof.h1@wp.pl)
It adds a fallback for CPU cache size detection. According to Sun
documentation, it is possible to have SMP system with SM40 modules.
Signed-off-by: Krzysztof Helt (krzysztof.h1@wp.pl)
---
It is added after sparc64 architecture.
Regards,
Krzysztof
----------------------------------------------------
Pensjonat Albatros? wypoczynek w pięknym zakątku Władysławowa.
O krok od plaży, atrakcyjne ceny, dobrze wyposażone pokoje.
Czegóż chcieć więcej? Zapamiętaj: albatros.gda.pl - Kliknij:
http://klik.wp.pl/?adr=www.albatros.gda.pl&sid=841
[-- Attachment #2: sparc32-max-cache-fix.patch --]
[-- Type: application/octet-stream, Size: 646 bytes --]
diff -urp linux-2.6.17/arch/sparc/kernel/smp.c linux-new/arch/sparc/kernel/smp.c
--- linux-2.6.17/arch/sparc/kernel/smp.c 2006-08-10 08:58:31.000000000 +0200
+++ linux-new/arch/sparc/kernel/smp.c 2006-08-12 19:11:20.000000000 +0200
@@ -79,6 +78,9 @@ void __cpuinit smp_store_cpu_info(int id
cache_nlines = 0x8000;
cache_nlines = prom_getintdefault(cpu_node, "ecache-nlines", cache_nlines);
max_cache_size = cache_line * cache_nlines;
+ /* this is for SM40 SuperSparc modules */
+ if (max_cache_size == 0)
+ max_cache_size = 36 * 1024;
}
if (cpu_data(id).mid < 0)
panic("No MID found for CPU%d at node 0x%08d", id, cpu_node);
next reply other threads:[~2006-08-12 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 19:14 Krzysztof Helt [this message]
2006-08-25 23:24 ` [PATCH] sparc32: max_cache_size fallback David Miller
2006-08-26 8:59 ` Krzysztof Helt
2006-08-26 23:48 ` David Miller
2006-08-28 18:33 ` Krzysztof Helt
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=44de28a4e7531@wp.pl \
--to=krzysztof.h1@wp.pl \
--cc=sparclinux@vger.kernel.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.