Subject: pool_init ordering problem on sun3
To: None <email@example.com>
From: Chuck Silvers <firstname.lastname@example.org>
Date: 01/22/2005 09:17:36
one of the problems with the sun3 port is that cpu_startup() ends up
allocating from a pool (uvm_mapent_pool, from the uvm_map() call in
dvma_init()), but pool link-set initializer stuff hasn't been called yet.
moving the call to link_pool_init() to before cpu_startup() makes sun3
happy, does anyone see that this would cause a problem on other platforms?