From owner-cvs-all Sat Sep 7 16:34:29 2002 Delivered-To: cvs-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 6A47237B400; Sat, 7 Sep 2002 16:34:23 -0700 (PDT) Date: Sat, 7 Sep 2002 16:34:23 -0700 From: Juli Mallett To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha machdep.c src/sys/i386/i386 machdep.c src/sys/ia64/ia64 machdep.c src/sys/pc98/i386 machdep.c src/sys/sparc64/sparc64 machdep.c Message-ID: <20020907163423.A14528@FreeBSD.org> References: <200209071912.g87JCs0I062248@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200209071912.g87JCs0I062248@freefall.freebsd.org>; from jmallett@FreeBSD.org on Sat, Sep 07, 2002 at 12:12:53PM -0700 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * De: Juli Mallett [ Data: 2002-09-07 ] [ Subjecte: cvs commit: src/sys/alpha/alpha machdep.c src/sys/i386/i386 machdep.c src/sys/ia64/ia64 machdep.c src/sys/pc98/i386 machdep.c src/sys/sparc64/sparc64 machdep.c ] > jmallett 2002/09/07 12:12:53 PDT > > Modified files: > sys/alpha/alpha machdep.c > sys/i386/i386 machdep.c > sys/ia64/ia64 machdep.c > sys/pc98/i386 machdep.c > sys/sparc64/sparc64 machdep.c > Log: > Fill out two fields (si_pid, si_uid) in the siginfo structure handed back > to userland in the signal handler that were not being iflled out before, but > should and can be. Note that until everything is refactored as I want, I can't make these fields "honest", about who's sending the signal, just about who the signal is being delivered to. I'm now torn, do I want to continue to push just to break the kernel API for signal senders, or do I want to push to also use siginfo's instead of signal numbers, in the kernel? This would allow code sending signals to send *much* more information, too. SVR4 uses siginfo much more "nicely" than we use things, I think. Being able to get meaningful information is very nice. It might also be possible to implement some of the shiny signal-based poll mechanisms, given the ability to pack somewhat arbitrary data into the siginfo structure. We also have plenty of room for growth in it, not that FreeBSD has an in-use ABI for siginfo, really. juli (who's ashamed to admit to having fun in the kernel) -- Juli Mallett | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message