tagging freebios2 tree

YhLu YhLu at tyan.com
Tue Nov 2 21:34:00 CET 2004

For DP Xeon MB, CONFIG_MAX_CPUS should be 4 or 2?

It is used only by you said stack....

config/linuxbios_ram.ld:                . = (CONFIG_MAX_CPUS * STACK_SIZE) ;
cpu/x86/pae/pgtbl.c:    static struct pg_table pgtbl[CONFIG_MAX_CPUS]
__attribute__ ((aligned(4096)));
cpu/x86/pae/pgtbl.c:    static unsigned long mapped_window[CONFIG_MAX_CPUS];
cpu/x86/pae/pgtbl.c:    if ((index < 0) || (index >= CONFIG_MAX_CPUS)) {


-----Original Message-----
From: ebiederman at lnxi.com [mailto:ebiederman at lnxi.com] 
Sent: Tuesday, November 02, 2004 5:06 PM
To: Li-Ta Lo
Cc: LinuxBIOS
Subject: Re: tagging freebios2 tree

Li-Ta Lo <ollie at lanl.gov> writes:

> On Tue, 2004-08-24 at 19:07, Eric W. Biederman wrote:
> > No quite I put the cpu_info structure at the bottom of the stack,
> > and this function looks it up.
> > 
> > The same idea has been used in the kernel for quite a while.  
> > 
> > Basically this allows me to preallocate some per cpu information
> > and to pass that into cpu_initialize from another cpu.
> > 
> > The linux kernel has been doing something similar for quite a while.
> > 
> Does cpu_info() return different value depends on which CPU it is 
> running ?

Yes.  The stack is per cpu and it returns a fixed address from
the stack structure.

 > Are the data structures per CPU or shared between CPUs ?

per-cpu.  Which is the point.

Linuxbios mailing list
Linuxbios at clustermatic.org

More information about the coreboot mailing list