From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Dom0 crash with old style AMD NUMA detection Date: Fri, 21 Sep 2012 13:48:34 -0400 Message-ID: <20120921174833.GC6821@phenom.dumpdata.com> References: <501BC20F.3040205@amd.com> <20120803123628.GB10670@andromeda.dapyr.net> <20120817142237.GA8467@phenom.dumpdata.com> <505CA8AB.6000808@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <505CA8AB.6000808@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andre Przywara Cc: Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , xen-devel , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org > Acked-by: Andre Przywara > > I compiled and boot-tested this on my (single node ;-) test box. > First bare-metal, dmesg: No NUMA configuration found > Then again, but with numa=off on the cmd-line: NUMA turned off > Then under Xen as Dom0 kernel: NUMA turned off > > So the code behaves under Xen as one would have explicitly specified > numa=off, which is what we want. Right. > I couldn't get hold of the test machine (old K8 server) that the bug > was once triggered, that's why I'm reluctant to give my Tested-by. > Will try this ASAP. OK, will wait with this - it would be a bit silly if the patch did not fix the issue :-)