Re: Core Topology
Rene Gollent <[email protected]> Mon, 23 Mar 2009 08:46:06 -0500
| Newsgroups | gmane.os.openbeos.kernel.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Mar 22, 2009 at 12:06 PM, Ingo Weinhold <[email protected]> wrote: > I'd prefer <cpu.h> to already offer a tree representation. I would introduce > a cpu_scope structure (or class) representing a tree node. The leaf nodes > would refer to the cpu_ents (respectively with C++ the cpu_ents (CPU) would > derive from cpu_scope (CPUScope)). Each node would describe the properties of > the corresponding hardware, e.g. what kind of hardware it refers to (CPU, > core, hardware thread,...) and what resources are shared by its children > (units, caches, busses, whatever). That works for me, just need to wrap my head around where / how all the CPU detection information is split up in the kernel since I see some of it happens in the boot loader and some in the actual kernel. Not sure yet if anything extra will be necessary to pick up the topology data, though I was under the impression at least some of that required ACPI. Regards, Rene ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com