From: Caspar Zhang <caspar@casparzhang.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] syscalls/numa: check syscall availability
Date: Wed, 08 Aug 2012 22:11:26 +0800 [thread overview]
Message-ID: <5022738E.4010201@casparzhang.com> (raw)
In-Reply-To: <11850AA3-DB90-4525-B168-AF39B8B4B373@gmail.com>
On 08/08/2012 05:46 PM, Garrett Cooper wrote:
> On Aug 8, 2012, at 2:29 AM, Caspar Zhang wrote:
>
>> On 07/31/2012 11:57 AM, Garrett Cooper wrote:
>>> On Mon, Jul 30, 2012 at 7:53 PM, Caspar Zhang <caspar@casparzhang.com> wrote:
>>>>
>>>> some NUMA related syscalls: mbind, get_mempolicy are not supported on
>>>> some arches (e.g. i386), I use TEST macro to test the syscall in setup()
>>>> function, if the syscall is not implemented on the system, a TCONF
>>>> message will given like this:
>>>>
>>>> get_mempolicy01 1 TCONF : syscall __NR_get_mempolicy01 not supported on your arch
>>>
>>> Using TEST isn't necessary to be honest: the syscall wrapper
>>> handles the (if you add a comment as to why things are being done in a
>>> single line, untested, that should be ok).
>>> Thanks!
>>> -Garrett
>>>
>>
>> Hi Garrett, sorry I'm kind of not catching you :-( what's your suggestion of correcting/improving this message?
>
> I'd remove "TEST(..)" from the line and just use the syscall function call.
> If you want, we can make syscall more explicit as far as a custom wrapper goes.
OK, I'll remove TEST() and resend the patch.
Thanks,
Caspar
> Cheers!
> -Garrett
>
------------------------------------------------------------------------------
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
prev parent reply other threads:[~2012-08-08 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 10:19 [LTP] [PATCH 0/2] numa_helper: get nodes with mem/cpu/both Jan Stancek
2012-07-20 10:19 ` [LTP] [PATCH 1/2] numa_helper: add flag to get_allowed_nodes() Jan Stancek
2012-07-20 10:19 ` [LTP] [PATCH 2/2] update testcases to use flag for get_allowed_nodes() Jan Stancek
2012-07-20 11:02 ` [LTP] [PATCH 0/2] numa_helper: get nodes with mem/cpu/both Caspar Zhang
2012-07-20 11:28 ` Jan Stancek
2012-07-26 10:14 ` Jan Stancek
2012-07-26 11:21 ` Caspar Zhang
2012-07-31 2:53 ` [LTP] [PATCH] syscalls/numa: check syscall availability Caspar Zhang
2012-07-31 3:57 ` Garrett Cooper
2012-08-08 9:29 ` Caspar Zhang
2012-08-08 9:46 ` Garrett Cooper
2012-08-08 14:11 ` Caspar Zhang [this message]
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=5022738E.4010201@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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