From: Frank Rowand <frank.rowand@am.sony.com>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
"Rowand, Frank" <Frank_Rowand@sonyusa.com>,
Thomas Gleixner <tglx@linutronix.de>,
rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] RFC - rt-tools: Detect whether numa is available at build time
Date: Mon, 28 May 2012 17:49:36 -0700 [thread overview]
Message-ID: <4FC41D20.1010105@am.sony.com> (raw)
In-Reply-To: <1337989189-17563-1-git-send-email-jkacur@redhat.com>
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@redhat.com>
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@am.sony.com>
-Frank
next prev parent reply other threads:[~2012-05-29 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 23:39 [PATCH] RFC - rt-tools: Detect whether numa is available at build time John Kacur
2012-05-29 0:49 ` Frank Rowand [this message]
2012-05-30 19:58 ` John Kacur
2012-05-30 21:48 ` Frank Rowand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC41D20.1010105@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=Frank_Rowand@sonyusa.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox