Re: [PATCH] Get rid of non portable _syscall0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lon Hohberger wrote:
>
> Similarly, the code is written to rely on the documented behavior.  So,
> when it's not available, maybe the wrapper should return
> (pid_t)pthread_self() instead of -ENOSYS?

I threw -ENOSYS in mostly as a sanity check.  If the suite is meant to be
portable to other POSIX systems, you'll certainly want to do something
else if gettid() doesn't exist, since it's linux-specific.  The only aim
of the patch was to shoot for portability accross all Linux platforms
(many of which don't have _syscall magic macros, and word on the street is
that we may not have them on any arches in the future).

... Adam


--

Linux-cluster@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux