ACPI: break procfs handlers for acpi events and debug levels out of drivers/acpi/system.c and into their own files.

First, we remove acpi_system_driver, since it's not really a driver, and making it its own 
object is just silly. This allows us to not have to register it, and we can hence remove
the add and remove callbacks. 

For initialization, acpi_system_add_fs() has been inlined in acpi_system_init(). The proc file
creation was cleaned up to use create_proc_read_entry() where possible. Any failures now
result in a goto Error, which prints the error message previously replicated after each
failure. We also remove all the files that were created if that happens. acpi_system_init()
was made a subsys_initcall and declared static. 

The acpi_system_exit() code and friends was removed, since it's never, ever called. 

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-acpi

struct acpi_system was removed, because it was an unncessary abstraction (a single array suffices).
All functions have been updated to reference the array. 

Unnecessary headers were removed, including ones implicitly included.

procfs files controlling sleep support were moved. 

sysrq handler and registration were removed. 

acpi_sleep_init() made an implicit subsys_initcall.

252 for exit_group

into groveronline.com:/root/bk/linux-acpi

- Use early table mapping code from acpitable.c (Andi Kleen)
- Make a warning a little more verbose

This fixes the old-pthreads breakage i can reproduce.

the fix is to only do the thread-group exit-completion logic in case of
thread-groups.

This is another step to have better threading support under Linux, it
implements the sys_exit_group() system call.

It's a straightforward extension of the generic 'thread group' concept,
which extension also comes handy to solve a number of problems when
implementing POSIX threads.

POSIX exit() [the C library function] has the following semantics: all
thread have to exit and the waiting parent has to get the exit code that
was specified for the exit() function.  It also has to be ensured that
every thread has truly finished its work by the time the parent gets the
notification.  The exit code has to be propagated properly to the parent
thread even if not the thread group leader calls the exit() function.

Normal single-thread exit is done via the pthread_exit() function, which
calls sys_exit().

Previous incarnations of Linux POSIX threads implementations chose the
following solution: send a 'thread management' signal to the thread
group leader via tkill(), which thread goes around and kills every
thread in the group (except itself), then calls sys_exit() with the
proper exit code.  Both old libpthreads and NGPT use this solution.

This works to a certain degree, unless a userspace threading library
uses the initial thread for normal thread work [like the new
libpthreads], which 'work' can cause the initial thread to exit
prematurely.

At this point the threading library has to catch the group leader in
pthread_exit() and has to keep the management thread 'hanging around'
artificially, waiting for the management signal. Besides being slightly
confusing to users ('why is this thread still around?') even this variant
is unrobust: if the initial thread is killed by the kernel (SIGSEGV or any
other thread-specific event that triggers do_exit()) then the thread goes
away without the thread library having a chance to intervene.

the sys_exit_group() syscall implements the mechanism within the kernel,
which, besides robustness, is also *much* faster. Instead of the threading
library having to tkill() every thread available, the kernel can use the
already existing 'broadcast signal' capability. (the threading library
cannot use broadcast signals because that would kill the initial thread as
well.)

as a side-effect of the completion mechanism used by sys_exit_group() it
was also possible to make the initial thread hang around as a zombie until
every other thread in the group has exited. A 'Z' state thread is much
easier to understand by users - it's around because it has to wait for all
other threads to exit first.

and as a side-effect of the initial thread hanging around in a guaranteed
way, there are three advantages:

 - signals sent to the thread group via sys_kill() work again. Previously
   if the initial thread exited then all subsequent sys_kill() calls to
   the group PID failed with a -ESRCH.

 - the get_pid() function got faster: it does not have to check for tgid
   collision anymore.

 - procps has an easier job displaying threaded applications - since the
   thread group leader is always around, no thread group can 'hide' from
   procps just because the thread group leader has exited.

 [ - NOTE: the same mechanism can/will also be used by the upcoming
     threaded-coredumps patch. ]

there's also another (small) advantage for threading libraries: eg. the
new libpthreads does not even have any notion of 'group of threads'
anymore - it does not maintain any global list of threads. Via this
syscall it can purely rely on the kernel to manage thread groups.

the patch itself does some internal changes to the way a thread exits: now
the unhashing of the PID and the signal-freeing is done atomically. This
is needed to make sure the thread group leader unhashes itself precisely
when the last thread group member has exited.

(the sys_exit_group() syscall has been used by glibc's new libpthreads
code for the past couple of weeks and the concept is working just fine.)

I forgot to remove an unused label in the deadlock fix patch.

Remove pty.o from the export-objs list, since pty.c does not export
any symbols.

A /* EXPORT_SYMBOL */ comment may have fooled the original author.

Removed compatibility cruft from zftape_syms.c.
There is no need to be compatible with kernel 2.1.18 and older.
Replaced FT_KSYM with direct call to EXPORT_SYMBOL.

- signal update; make do_signal use generic get_signal_to_deliver()
- irqs_disabled macro
- remove vmlinux.lds.s target from arch/alpha/Makefile since it works
  correctly in the top level Makefile
- extra argument for pcibios_enable_device (most likely we'll never
  use it though...)

  clean up with bio_kmap_irq() thing properly. remove the micro optimization of _not_ calling kmap_atomic() if this isn't a highmem page. we could keep that and do the inc_preempt_count() ourselves, but I'm not sure it's worth it and this is cleaner.

into hera.kernel.org:/home/axboe/BK/linux-2.5-ide

to bio_kmap/kunmap_irq(), which would screw the preemption count. pass
in rq to ide_unmap_buffer() as well to make the right decision.

o silly IS_PDC4030_DRIVE definition

silly old irq and region registration etc.

o byte -> u8
o use atapi register definitions
o update to ide-iops changes
o driver->end_request() changes
o update to new ide-dma api
o ->reinit to ->attach

o byte -> u8

o ide-iops changes (mainly moving stuff to ide-iops.c)
o byte -> u8
o update to new ide-dma api
o driver->end_request changes
o various style cleanups
o remove ALTSTAT_SCREW_UP stuff
o WAIT_CMD -> WAIT_WORSTCASE interrupt timeout
o add (commented out) various ata commands to match 2.4.20-pre5-ac
o move the flagged_* interrupt handlers

o byte -> u8
o remove various register structs, it's ide general now
o ide-iops changes
o various style cleanups
o update to new ide-dma api
o remove idetape_do_end_request(), dupe of ide core helper
o ->reinit to ->attach changes

o remove low level driver ifdef mess
o allow "host" to register into proc list instead

o byte -> u8
o drive_is_flashcard() moved to probe code
o ide-iops changes
o various cleanups
o remove useless ide_lock debug stuff

o remove *_FUNC abstraction
o remove MODULE ifdefs
o small style changes

o byte -> u8
o small style cleanups

o byte -> u8
o remove various status register definitions, these are now ata (atapi)
  generic
o ide-iops changes
o remove idefloppy_end_request(), dupe of ide core helper
o driver->end_request changes
o lots of style cleanups
o update to new dma interface
o ->reinit to ->attach updates

o ide-iops changes
o driver->end_request and ide_end_request changes
o ->dmaproc() is now split into separate functions
o work on new mmio adapters
o init cleanup

o ide-iops changes
o ide_end_request() now takes a nr_sectors argument, driver->end_request
  as well
o remove idedisk_end_request(), it's a duplicate of ide core helper
o byte -> u8
o ->reinit is now ->attach (to match 2.4.20-pre5-ac)

o kill silly ide_cdrom_end_reuquest() function, it only duplicates
  ide core code.
o use the atapi error, status, ireason, etc types
o use ide-iops functions, not IN_BYTE etc
o use blk_fs_request() where appropriate
o limit retries on MEDIUM_ERROR sense key
o use new ide_end_request() that handles nr_sectors
o rename ->reinit to ->attach