Re: [PATCH 3 of 3] x86: clean up memory corruption check and add more kernel parameters
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Sun, 7 Sep 2008 11:11:12 +0200
* Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
+ memory_corruption_check=0/1 [X86]
could you please add a second .config parameter as well:
CONFIG_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
which turns this parameter 1 without having to specify it on the boot
command line. That way -tip's randconfig testing can check this on a
couple of boxes and the WARN() will be detected automatically.
Also, i'd suggest to make the defaults of the scanning parameters be as
widely enabled as reasonable - we want to see how much real problems
this can catch.
+config X86_CHECK_BIOS_CORRUPTION
+ bool "Check for low memory corruption"
+ default y
please make it default-disabled.
Looks good otherwise.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- [PATCH 4/3] x86: default corruption check to off, but put parameter default in Kconfig
- From: Jeremy Fitzhardinge
- [PATCH 4/3] x86: default corruption check to off, but put parameter default in Kconfig
- Prev by Date: Re: [PATCH] x86: cpu make amd.c more like amd_64.c
- Next by Date: ia64 start secondary cpus: what's the first line where interrupts can arrive?
- Previous by thread: [PATCH 2.6.28] m68k: init_irq_proc depends on CONFIG_PROC_FS
- Next by thread: [PATCH 4/3] x86: default corruption check to off, but put parameter default in Kconfig
- Index(es):
Relevant Pages
|
