Re: allocating memory during kernel startup

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

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

Hello,

On May 7, 2010, at 3:45 PM, Martin Husemann wrote:

> On Fri, May 07, 2010 at 08:39:51PM +0100, Mindaugas Rasiukevicius  
> 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, ...

It doesn't allocate any screens ( that's wsdisplay, not rasops ), only  
some memory for box drawing characters which are strictly optional -  
it can live happily without them and its not like we need them for  
kernel output anyway. All it needs is a sane way to decide wether it  
can allocate memory or not.

have fun
Michael

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

iQEVAwUBS+RyispnzkX8Yg2nAQI2eAf8C1THaTziezZwl5aIoZrs0Wtljh+OZ0Ms
igoGuYs1AwfIiqNCdrGerwRAO3QYvOq7mT1QDkOyL5hWWfWrpfU180S/p4kshni2
GUKB5D7UklTw544A9P9G7utyHt9mPE36rxbKy959jeNi0MZFSQ2BogZcOKMnf1lK
aZ801gLIBM1Sbfy3cc6Xhnqh6TojeHxmh30095lXgJMcBF/GiHGw1G/Qd/fhkGbv
CY5rg5hdQFXRQAMsqYp/WKtxM91Othyb92XN83+duUvqNpgGmeKyWpeUKu/f+CyI
enD/9nqt2WT6IIDmcKXT5//Br/XLlq+YIod2sftxPtOG8/lsfPbFkA==
=iA/O
-----END PGP SIGNATURE-----