From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Rowand Subject: Re: [PATCH] RFC - rt-tools: Detect whether numa is available at build time Date: Mon, 28 May 2012 17:49:36 -0700 Message-ID: <4FC41D20.1010105@am.sony.com> References: <1337989189-17563-1-git-send-email-jkacur@redhat.com> Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Clark Williams , "Rowand, Frank" , Thomas Gleixner , rt-users To: John Kacur Return-path: Received: from va3ehsobe001.messaging.microsoft.com ([216.32.180.11]:8696 "EHLO va3outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751423Ab2E2AuE (ORCPT ); Mon, 28 May 2012 20:50:04 -0400 In-Reply-To: <1337989189-17563-1-git-send-email-jkacur@redhat.com> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On 05/25/12 16:39, John Kacur wrote: > This is a preliminary hack, I need to clean it up a little, but incase you > want to give it a try, here is the alpha version. > > Note - I stole this methodology from tools/perf > > Signed-off-by: John Kacur I knew I would regret suggesting this fix. It works fine on my fedora 12 x86_64 system for native build. It works fine on my fedora 12 x86_64 system for crossbuild for ARM. The NUMA=0 option is still useful (thank you for leaving that in place). I have a second ARM target board, where the cross linker does not complain about libnuma, so cyclictest is build with libnuma. But my run time environment does not have a libnuma. Ah the joy of pre-release file systems. The NUMA=0 option allowed me to properly build cyclictest to run on this not quite yet finished file system. Tested-by: Frank Rowand -Frank