On Wed, Jul 23, 2008 at 11:59:53AM +0530, Sharyathi Nagesh wrote: > Hi > I have developed 2 test cases for getcpu() system call, Test cases > check minimal functionality of getcpu(). These test cases have a > requirement of kernel 2.6.20 and above and glibc 2.6 and above. > Currently the system call is implemented on i386 and x86_64 > architecture, in x86_64 it is implemented as virtual system call. I felt > the best way to call these system calls is to use the interface provided > by glibc in x86_64 > Man page of getcpu() can be found here: > http://www.kernel.org/doc/man-pages/online/pages/man2/getcpu.2.html
Sorry for the late feedback. I don't understand what you're testing in getcpu2 -- getcpu() has no input arguments (except for the cache). So why do you expect it to fail with 0xff? -Andi ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
