Re: allocating memory during kernel startup

[Michael <macallan%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On May 7, 2010, at 4:01 PM, Mindaugas Rasiukevicius wrote:

> Martin Husemann <martin%duskware.de@localhost> wrote:
> > > Well, kmem(9) is initialised very early, just after pool(9), in  
> > > uvm_init
> > > (), where I moved it couple years ago.  Yes, 'cold' is unset very  
> > > late.
> > > Since allocation gets postponed anyway, is that a problem?  You  
> > > did not
> > > describe your use case. :)
> >
> > consinit(), run just before uvm_init().
> >
> > It may need to initialize raspos, which will allocate memory for  
> > fonts,
> > screens, ...
>
> OK, that is something I am not familiar with.  Any reason why one  
> could
> not have rasops_sysinit() after uvm_init()?

If anything goes wrong in uvm_init() you don't see any output.

> I see consinit() as a bare minimum to printf() very early errors  
> (which should not happen, normally).

Exactly, the parts that need uvm are strictly optional - not needed at  
all for basic kernel output. We only need to know if we can use them  
or not.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBS+Ry/MpnzkX8Yg2nAQLrgQf+NvuRy4jaQCCCkNeWlIvk1rAn0gJdNnTg
XzUZHkUWKWWuXha8kX8cefRff07s2eE9M7re3uaBsQT4DUG/qks5/DltmR19NcvP
QDJHhCM9sZhAlmXge/eRp7fFbuyuraCdPDos+0nJ/sBN+1790Gb4/2Bqb1iQsLuZ
bsdeV5fHwTduL2kZHDts6LvSwVr1j1C6nnbj7T1JrDRhpiF45KMki+8GXYkglhww
lY0qffrmHI6ORPuusQE8DXDD+rdwl1NhSBDH8YbyftHbDr7r2YnVmRBH/livZd0F
ibWOUe3eJKt/XxkGDgEFJditn/URkysulU6YTfbxRVTMtEY4YTWEZg==
=YbXx
-----END PGP SIGNATURE-----