Date: Sun, 22 Nov 2009 14:32:32 +0000 (UTC) From: Jun Kuriyama <kuriyama@FreeBSD.org> To: cvs-src-old@freebsd.org Subject: cvs commit: src/sys/amd64/amd64 initcpu.c machdep.c src/sys/amd64/include md_var.h src/sys/i386/i386 initcpu.c Message-ID: <200911221433.nAMEXKY9004640@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
kuriyama 2009-11-22 14:32:32 UTC
FreeBSD src repository
Modified files: (Branch: RELENG_8)
sys/amd64/amd64 initcpu.c machdep.c
sys/amd64/include md_var.h
sys/i386/i386 initcpu.c
Log:
SVN rev 199648 on 2009-11-22 14:32:32Z by kuriyama
- MFC r199067,199215,199253
- Add hw.clflush_disable loader tunable to avoid panic (trap 9) at
map_invalidate_cache_range() even if CPU is not Intel.
- This tunable can be set to -1 (default), 0 and 1. -1 is same as
current behavior, which automatically disable CLFLUSH on Intel CPUs
without CPUID_SS (should be occured on Xen only). You can specify 1
when this panic happened on non-Intel CPUs (such as AMD's). Because
disabling CLFLUSH may reduce performance, you can try with setting 0
on Intel CPUs without SS to use CLFLUSH feature.
- Amd64 init_secondary() calls initializecpu() while curthread is
still not properly set up. r199067 added the call to
TUNABLE_INT_FETCH() to initializecpu() that results in hang because
AP are started when kernel environment is already dynamic and thus
needs to acquire mutex, that is too early in AP start sequence to
work.
Extract the code that should be executed only once, because it sets
up global variables, from initializecpu() to initializecpucache(),
and call the later only from hammer_time() executed on BSP. Now,
TUNABLE_INT_FETCH() is done only once at BSP at the early boot
stage.
Revision Changes Path
1.54.2.4 +21 -1 src/sys/amd64/amd64/initcpu.c
1.707.2.5 +1 -0 src/sys/amd64/amd64/machdep.c
1.86.2.2 +1 -0 src/sys/amd64/include/md_var.h
1.62.2.3 +16 -1 src/sys/i386/i386/initcpu.c
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200911221433.nAMEXKY9004640>