From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933114AbZE0UQy (ORCPT ); Wed, 27 May 2009 16:16:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761866AbZE0UMt (ORCPT ); Wed, 27 May 2009 16:12:49 -0400 Received: from one.firstfloor.org ([213.235.205.2]:35933 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756240AbZE0UMr (ORCPT ); Wed, 27 May 2009 16:12:47 -0400 From: Andi Kleen References: <200905271012.668777061@firstfloor.org> In-Reply-To: <200905271012.668777061@firstfloor.org> To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, fengguang.wu@intel.com Subject: [PATCH] [14/16] HWPOISON: FOR TESTING: Enable memory failure code unconditionally Message-Id: <20090527201240.F0CDA1D0286@basil.firstfloor.org> Date: Wed, 27 May 2009 22:12:40 +0200 (CEST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Normally the memory-failure.c code is enabled by the architecture, but for easier testing independent of architecture changes enable it unconditionally. This should not be merged into mainline. Signed-off-by: Andi Kleen --- mm/Kconfig | 2 ++ 1 file changed, 2 insertions(+) Index: linux/mm/Kconfig =================================================================== --- linux.orig/mm/Kconfig 2009-05-27 21:14:21.000000000 +0200 +++ linux/mm/Kconfig 2009-05-27 21:19:16.000000000 +0200 @@ -228,6 +228,8 @@ config MEMORY_FAILURE bool + default y + depends on MMU config NOMMU_INITIAL_TRIM_EXCESS int "Turn on mmap() excess space trimming before booting"