public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Zhouping Liu <zliu@redhat.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 1/3] m4/ltp-numa.m4: fixed numa config
Date: Sat, 28 Apr 2012 19:35:57 +0800	[thread overview]
Message-ID: <4F9BD61D.8010705@cn.fujitsu.com> (raw)
In-Reply-To: <9f6a3874d522c848218b164f61ff207760ed2b22.1335599279.git.zliu@redhat.com>

On 04/28/2012 03:48 PM, Zhouping Liu wrote:

> numa_alloc_onnode() and numa_move_pages() all need numa lib '-lnuma',
> but in ltp-numa.m4, we just checked the two functions using
> AC_CHECK_FUNCS, without the patch, it always report such error
> log in numa system: "undefined reference to `numa_alloc_onnode`",
> which blocked syscalls/move_pages/* cases, the patch fixed it.



pushed the series, thanks

Wanlong Gao

> 
> Signed-off-by: Zhouping Liu <zliu@redhat.com>
> ---
>  m4/ltp-numa.m4 |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/m4/ltp-numa.m4 b/m4/ltp-numa.m4
> index bcc5e6b..d03bc80 100644
> --- a/m4/ltp-numa.m4
> +++ b/m4/ltp-numa.m4
> @@ -26,7 +26,14 @@ AC_DEFUN([LTP_CHECK_SYSCALL_NUMA],
>  [dnl
>  AC_CHECK_HEADERS([linux/mempolicy.h numa.h numaif.h],[
>  	LTP_SYSCALL_NUMA_HEADERS=yes
> -	AC_CHECK_FUNCS(numa_alloc_onnode,numa_move_pages)
> +	AC_CHECK_LIB(numa,numa_alloc_onnode,[have_numa_alloc_onnode="yes"])
> +	if  test "x$have_numa_alloc_onnode" = "xyes"; then
> +		AC_DEFINE(HAVE_NUMA_ALLOC_ONNODE,1,[define to 1 if you have 'numa_alloc_onnode' function])
> +	fi
> +	AC_CHECK_LIB(numa,numa_move_pages,[have_numa_move_pages="yes"])
> +	if  test "x$have_numa_move_pages" = "xyes"; then
> +		AC_DEFINE(HAVE_NUMA_MOVE_PAGES,1,[define to 1 if you have 'numa_move_pages' function])
> +	fi
>  ]
>  	AC_CHECK_LIB(numa,numa_available,[
>  NUMA_CPPFLAGS="-DNUMA_VERSION1_COMPATIBILITY"



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2012-04-28 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-28  7:48 [LTP] [PATCH 1/3] m4/ltp-numa.m4: fixed numa config Zhouping Liu
2012-04-28  7:48 ` [LTP] [PATCH 2/3] syscalls/move_pages: modified HAS_NUMA_H as HAVE_NUMA_H Zhouping Liu
2012-04-28  7:53   ` Garrett Cooper
2012-04-28  7:56   ` Caspar Zhang
2012-04-28  7:48 ` [LTP] [PATCH 3/3] syscalls/move_pages: removed tst_exit in check_config() Zhouping Liu
2012-04-28  7:56   ` Caspar Zhang
2012-04-28  7:57 ` [LTP] [PATCH 1/3] m4/ltp-numa.m4: fixed numa config Caspar Zhang
2012-04-28 11:35 ` Wanlong Gao [this message]
     [not found] <5f459a2d-8dca-42ca-bff1-bd96d9e019a4@zmail13.collab.prod.int.phx2.redhat.com>
2012-04-28  9:05 ` Zhouping Liu

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=4F9BD61D.8010705@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=zliu@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