On Tue, May 29, 2012 at 2:49 AM, Frank Rowand <frank.rowand@xxxxxxxxxxx> wrote: > > 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 <jkacur@xxxxxxxxxx> > > 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.rowand@xxxxxxxxxxx> > Thank you very much for testing my quick hack. (tglx has anointed it the beer on the couch hack) What happens when you run a compiled with libnuma binary on a ARM target that doesn't have numa, as long as you don't supply the numa function? Thanks John -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
