public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Caspar Zhang <caspar@casparzhang.com>
To: Christopher Yeoh <cyeoh@au1.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Simple tests for cross memory attach (process_vm_[readv|writev] syscalls)
Date: Wed, 11 Jul 2012 18:14:40 +0800	[thread overview]
Message-ID: <4FFD5210.1070305@casparzhang.com> (raw)
In-Reply-To: <20120518180534.088a07b2@Gantu>

On 05/18/2012 04:35 PM, Christopher Yeoh wrote:
> On Tue, 15 May 2012 10:56:17 -0400 (EDT)
> Jan Stancek <jstancek@redhat.com> wrote:
>>
>> Hi,
>>
>> I looked at testcases sent by Chris. Good news is, they
>> do not overlap (in terms of functionality) with mine :-).
>>
>> The patch need some polishing to match the style guide:
>> - indentation
>> - I think output should be TINFO, rather than plain printf
>> - single statement if without { }
>> - I would split some code to more functions, for example
>> process_vm_writev01.c main function seems complex
>
> Thanks for the feedback. I'll have a go at reworking them.
>
>> As for test organization, I think we need to decide 2 issues:
>> 1. directory structure
>> a)
>>    testcases/kernel/syscalls/cma/
>>    testcases/kernel/syscalls/cma/process_vm_readv
>>    testcases/kernel/syscalls/cma/process_vm_writev
>> b)
>>    testcases/kernel/syscalls/process_vm_readv
>>    testcases/kernel/syscalls/process_vm_writev
>>
>> I'm preferring a) as these 2 syscalls are closely related,
>> and we already have need to share code.
>
> that would be fine with me.
>
>> 2. how to invoke new syscalls
>> a)
>> Patch from Chris is defining new syscall numbers in test and
>> using syscall(2).
>>
>> b)
>> My patch adds configure check for glibc wrappers
>> process_vm_readv/writev and if those does not exists it checks for
>> __NR_process_vm_readv.
>>
>> I think we should not define syscall numbers in tests directly,
>> but I'm relying on LTP maintainers to provide guidance here.
>
> I agree - the configure check is much better. I was just trying to get
> something working :-)
>
> Regards,
>
> Chris
>

Hi Chris, not sure if you're working on a v2 to these CMA simple tests, 
if not, mind /me doing some update based on your version?

Thanks,
Caspar


------------------------------------------------------------------------------
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

  reply	other threads:[~2012-07-11 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 12:46 [LTP] [PATCH] Simple tests for cross memory attach (process_vm_[readv|writev] syscalls) Christopher Yeoh
2012-05-09 13:00 ` Caspar Zhang
2012-05-15 14:56   ` Jan Stancek
2012-05-17 14:26     ` Jan Stancek
2012-05-18  8:35     ` Christopher Yeoh
2012-07-11 10:14       ` Caspar Zhang [this message]
2012-05-18 12:35     ` Cyril Hrubis

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=4FFD5210.1070305@casparzhang.com \
    --to=caspar@casparzhang.com \
    --cc=cyeoh@au1.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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