From: Jun Sun <jsun@mvista.com>
To: Keith M Wesolowski <wesolows@foobazco.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: RFC: Cleanup/detection patch
Date: Tue, 03 Apr 2001 19:43:07 -0700 [thread overview]
Message-ID: <3ACA8A3B.8BBABB11@mvista.com> (raw)
In-Reply-To: 20010401235212.B9737@foobazco.org
Keith M Wesolowski wrote:
>
> I have posted an initial copy of my patch for machine detection,
> namespace cleanup, and promlib abstraction at
> http://foobazco.org/~wesolows/mips64-machine.diff. This is against
> 2.4.2 CURRENT oss. It currently passes my regression testsuite which
> unfortunately does not include an ip27 boot test.
>
Keith, I am interested in this stuff, but I have not got time around to look
into it.
Here are some of my thoughts on this issues. Maybe you can clarify them here.
1. Right now, our tree (at least 32-bit) does not even support multiple CPUs
(with the same machine/board). Take a look of
arch/mips/mm/loadmmu.c:loadmmu(), and you will see what I mean. The CPU
specific ld_mmu_xxx is #ifdef'ed. So if you enable multiple CPU, the last
ld_mmu_xxx will win!
So a modest step forward would be fixing that first.
2. Currently all CPU specific ld_mmu_xxx stuff lump cache and TLB together.
That is not very good. I have seen CPUs that can share cache but not TLB.
Vice versa. Personally I like to see their separation first before a more
dramatic scheme is in place.
3. Unfortunally not all CPUs can be fully probed at the run-time, specifically
the external cache size and geometry. I was thinking perhaps a board
detection routine should be placed at the beginning which will supply external
cache info. In addition it will probably set prom_init() pointer - yes, we do
have conflicting prom_init() from every board-specific implementation - and
board_setup() pointer. What do you think?
Sorry for not giving you patch specific comments, but I figure if I don't spit
it out now it will be probably never. :-)
Jun
next prev parent reply other threads:[~2001-04-04 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 6:52 RFC: Cleanup/detection patch Keith M Wesolowski
2001-04-04 2:43 ` Jun Sun [this message]
2001-04-04 3:30 ` Keith M Wesolowski
2001-04-04 17:54 ` Jun Sun
2001-04-05 7:46 ` Keith M Wesolowski
2001-04-05 20:29 ` Jun Sun
2001-04-05 21:03 ` Keith M Wesolowski
2001-04-05 21:53 ` Jun Sun
2001-04-09 6:40 ` Geert Uytterhoeven
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=3ACA8A3B.8BBABB11@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=wesolows@foobazco.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