From: "Kevin D. Kissell" <kevink@mips.com>
To: "Linux-MIPS Mailing List" <linux-mips@linux-mips.org>
Subject: Dubious MIPS kernel SMP Structures
Date: Wed, 17 Nov 2004 16:29:21 +0100 [thread overview]
Message-ID: <006d01c4ccba$36a43110$10eca8c0@grendel> (raw)
In arch/mips/kerenl/smp.c, there are two tables defined, __cpu_number_map[]
and __cpu_logical_map[], which would appear to provide forward and backward
mapping between a set of unique but arbitrary CPU numbers and a monotonically
increasing number 0..n of indices into per-CPU data. As near as I can tell, the
only use of this is in the sb1250 code for setting up interrupt hardware. Is there
a reason why it's defined at the mips/kernel level, and not down in the SiByte
platform subtree? Is there a generic, architectural definition of how these mappings
should and should not be set up and used?
Regards,
Kevin K.
next reply other threads:[~2004-11-17 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 15:29 Kevin D. Kissell [this message]
2004-11-17 16:46 ` Dubious MIPS kernel SMP Structures Ralf Baechle
2004-11-17 17:07 ` Kevin D. Kissell
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='006d01c4ccba$36a43110$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=linux-mips@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