Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 08 Dec 2005 12:48:59 +0800
From:      David Xu <davidxu@freebsd.org>
To:        Daniel Eischen <deischen@freebsd.org>
Cc:        Scott Long <scottl@samsco.org>, src-committers@freebsd.org, Doug Ambrisko <ambrisko@ambrisko.com>, John Baldwin <jhb@freebsd.org>, cvs-src@freebsd.org, cvs-all@freebsd.org
Subject:   Re: cvs commit: src/sys/sys signal.h
Message-ID:  <4397BB3B.2010008@freebsd.org>
In-Reply-To: <Pine.GSO.4.43.0512072210410.27928-100000@sea.ntplx.net>
References:  <Pine.GSO.4.43.0512072210410.27928-100000@sea.ntplx.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Eischen wrote:
> I was going to do it in libc so it doesn't have to be done by each
> thread library.
> 
> But there are still aio_* syscalls that haven't been changed to have
> compat syscalls.  You did aio_read, aio_write, and lio_listion, but
> not aio_error, aio_return, aio_suspend, aio_cancel, and aio_waitcomplete.
> I think these really need compat syscalls due to the different layout of
> struct sigevent (because it affects layout of struct aiocb).
> 
The aio_error, aio_return and other syscalls don't access sigevent,
they all access kernel private data of aiocb, I left old sigevent space 
there, but will not be used by new syscalls, the new sigevent is
appended at end of aiocb, offset of kernel private data area is not changed.

> I don't think Library-level shims aren't going to help in the case of
> statically built binaries.
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4397BB3B.2010008>