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, 09 May 2012 21:00:51 +0800 [thread overview]
Message-ID: <4FAA6A83.8010100@casparzhang.com> (raw)
In-Reply-To: <20120509221644.4d5f1819@Gantu>
On 05/09/2012 08:46 PM, Christopher Yeoh wrote:
> Hi,
>
> Here are some patches which add testcases for cross memory attach (CMA)
> functionality which is included in more recent kernels. CMA adds two
> new syscalls, process_vm_readv and process_vm_writev. Man pages for
> these two syscalls were added in the man-pages-3.40 release.
>
> The testcases aren't really ready for inclusion as-is, but I thought
> they could do with some review now. One issue is that the syscall
> wrappers were not included in glibc until glibc 2.15 which not all
> distributions have picked up yet. For the testcases to compile I have a
> header file with some hard coded syscall numbers included (just for
> x86/powerpc atm, but more could be added). These numbers won't change
> in the future, but its an obviously ugly workaround.
>
> Is this a show stopper problem? Do I have to wait until more
> distributions have picked up glibc 2.15 (or at least backported the
> glibc syscall wrappers) before it can be added to LTP? Or should I use
> some other workaround - eg detect if the syscalls are defined on the
> system and just not attempt to build the test if they aren't?
>
> The testcases are not that extensive yet, just coverage of basic
> functionality.
>
> Regards,
>
> Chris
>
Hi Chris, thanks very much for the patch, I tried to backport your
testcases in http://ozlabs.org/~cyeoh/cma/ to LTP and composed an
unfinished version, then I was busy for other things. I'm happy to see
you can backport it by yourself :) There are some more new cma patches
(aims on testing retcode and errnos) sent by Jan Stancek (cc-ed) [1], I
think we need to discuss the testcase organization..
And I will review the testcases when I get more free time.
Thanks,
Caspar
[1]
http://thread.gmane.org/gmane.linux.ltp/16052
http://thread.gmane.org/gmane.linux.ltp/16053
http://thread.gmane.org/gmane.linux.ltp/16054
http://thread.gmane.org/gmane.linux.ltp/16055
------------------------------------------------------------------------------
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
next prev parent reply other threads:[~2012-05-09 13:01 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 [this message]
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
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=4FAA6A83.8010100@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