[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AF233D1473C1364ABD51D28909A1B1B732714FE9@PGSMSX105.gar.corp.intel.com>
Date: Thu, 29 Jan 2015 09:59:35 +0000
From: "Ong, Boon Leong" <boon.leong.ong@...el.com>
To: Bryan O'Donoghue <pure.logic@...us-software.ie>
CC: "tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>, "x86@...nel.org" <x86@...nel.org>,
"dvhart@...radead.org" <dvhart@...radead.org>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] x86: Add Isolated Memory Regions for Quark X1000
Bryan, a minor fix on the config below...
>diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug index
>61bd2ad..fcf5701 100644
>--- a/arch/x86/Kconfig.debug
>+++ b/arch/x86/Kconfig.debug
>@@ -313,6 +313,18 @@ config DEBUG_NMI_SELFTEST
>
> If unsure, say N.
>
>+config DEBUG_IMR_SELFTEST
>+ bool "Isolated Memory Region self test"
>+ default n
>+ depends on INTEL_IMR
>+ ---help---
>+ This option enables automated sanity testing of the IMR code.
>+ Some simple tests are run to verify IMR bounds checking, alignment
>+ and overlapping. This option is really only useful if you are
>+ debugging an IMR memory map or are modifying the IMR code and
>want to
>+ test your changes.
>+
>+ If unsure say N here.
Miss a newline here.
> config X86_DEBUG_STATIC_CPU_HAS
> bool "Debug alternatives"
> depends on DEBUG_KERNEL
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists