Andrew Gallatin 919eea6db9 Check whether we need to do a full restore after handling ASTs. If ... an AST results in a signal being delivered, we'll need to do a full register restore so as to properly setup the signal handler. This is somewhat of a pessimization, because ast() will be called twice in this case. This fixes several problems that have been reported where signal intensive userland apps (most notably dump) have been SEGV'ing for no fault of their own. Thanks to Peter Jeremy <peter.jeremy@alcatel.com.au> for presenting the AST scenario which led to me fiinally figuring this out. Reviewed by: jhb		2001-03-28 01:19:41 +00:00
..
alpha	Check whether we need to do a full restore after handling ASTs. If	2001-03-28 01:19:41 +00:00
conf	Clean up some leftovers from the root mount cleanup that was done some	2001-02-04 15:35:10 +00:00
include	Unbreak build on alpha.	2001-03-24 15:17:27 +00:00
isa	Use the MI ithread helper functions in the alpha hardware interrupt code.	2001-02-09 17:53:23 +00:00
linux	- Call fork1() directly instead of calling rfork() so that it doesn't mask	2001-03-11 23:41:55 +00:00
mcbus	Doug found that doing a W1C on MCPCIA_INT_REQ just around the time you	2001-02-13 22:48:12 +00:00
osf1	Grab the process lock while calling psignal and before calling psignal.	2001-03-07 03:37:06 +00:00
pci	Use the MI ithread helper functions in the alpha hardware interrupt code.	2001-02-09 17:53:23 +00:00
tc	Another round of the <sys/queue.h> FOREACH transmogriffer.	2001-02-04 16:08:18 +00:00
tlsb	Send the remains (such as I have located) of "block major numbers" to	2001-03-26 12:41:29 +00:00
Makefile	Add a dopey makefile to do the tags dance, which is probably not perfect	2000-12-31 23:26:34 +00:00