d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

It is safe to initialize locks even on early boot (and it is the same

Browse Source 
thing all the other architectures already do) thus just initialize
kernel_pmap in pmap_bootstrap().

Reported by:	alc
Reviewed by:	alc, marius
Tested by:	flo, marius
Approved by:	re (kib)
MFC after:	1 week
This commit is contained in:
attilio 2011-09-19 18:29:15 +00:00
parent b20c15d80b
commit 420a3a3f8b
2 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
sys/sparc64/sparc64/machdep.c
View File

@ -597,11 +597,6 @@ sparc64_init(caddr_t mdp, u_long o1, u_long o2, u_long o3, ofw_vec_t *vec)
wrpr(pil, 0, 0);
wrpr(pstate, 0, PSTATE_KERNEL);
/*
* Finish pmap initialization now that we're ready for mutexes.
*/
PMAP_LOCK_INIT(kernel_pmap);
OF_getprop(root, "name", sparc64_model, sizeof(sparc64_model) - 1);
kdb_init();

4
sys/sparc64/sparc64/pmap.c
View File

@ -671,11 +671,9 @@ pmap_bootstrap(u_int cpu_impl)
/*
* Initialize the kernel pmap (which is statically allocated).
* NOTE: PMAP_LOCK_INIT() is needed as part of the initialization
* but sparc64 start up is not ready to initialize mutexes yet.
* It is called in machdep.c.
*/
pm = kernel_pmap;
PMAP_LOCK_INIT(pm);
for (i = 0; i < MAXCPU; i++)
pm->pm_context[i] = TLB_CTX_KERNEL;
CPU_FILL(&pm->pm_active);