Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753862AbbDHBqw (ORCPT ); Tue, 7 Apr 2015 21:46:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42765 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753767AbbDHBqt (ORCPT ); Tue, 7 Apr 2015 21:46:49 -0400 Date: Wed, 8 Apr 2015 09:46:30 +0800 From: Dave Young To: Xishi Qiu Cc: x86@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, bhe@redhat.com, akpm@linux-foundation.org, isimatu.yasuaki@jp.fujitsu.com, mingo@redhat.com, hpa@zytor.com Subject: Re: [PATCH V2] x86/numa: kernel stack corruption fix Message-ID: <20150408014630.GF7213@localhost.localdomain> References: <20150407134132.GA23522@dhcp-16-198.nay.redhat.com> <5524862F.6010709@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5524862F.6010709@huawei.com> User-Agent: Mutt/1.5.22.1-rc1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 22 > > > > - /* Mark all kernel nodes. */ > > + /* > > + * Mark all kernel nodes. > > + * > > + * In case booting with mem=nn[kMG] or in kdump kernel, numa_meminfo > > Hi Dave, > > It should both set mem=xx and numa=off, then numa_meminfo may not include all > the memblock.reserved memory, right? Yasuaki Ishimatsu suggests to remove numa=off in comment because in theory there's such possiblity that it may happen even without numa=off. Just consider the non-snb board.. Thanks Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/