into home.osdl.org:/home/torvalds/v2.5/linux

- Don't write the current time back to the RTC on suspend - we may
  jump over a programmed wakeup alarm.
- Restore SA1100 GPIO output state

- Suspend and resume system devices.
- If device suspend fails, don't suspend.

Some ARM CPUs don't allow CP15 CR1 control register to be read.
Therefore, to ensure that the value hits the control register on
Xscale, read back the CP15 CR0 ID register instead.

On ARM, we oops when we detect that an interrupt handler has unbalanced
the preempt count.  We should restore the preempt count when we started
to handle the interrupt and then cause the oops.

* replace previously removed NULL context check
  (causes oops when opening non existent device)

* replace previously removed NULL context check
  (causes oops when opening non existent device)

* add RCC underrun handling
* fix stats output typo
* replace previously removed NULL context check
  (causes oops when opening non existent device)

This fixes a "miscompile" HP reported against gcc 3.3 with
-march-pentium4.  It turned out to be a non-complete asm contraint.  the
existing constraint on "opt" was on the address of "opt", which allowed
gcc to reorder the setting of the fields inside opt to beyond the asm
that uses it, which is less than useful at best.

This changes the way futexes are indexed, so that they don't pin pages. 
It also fixes some bugs with private mappings and COW pages.

Currently, all futexes look up the page at the userspace address and pin
it, using the pair (page,offset) as an index into a table of waiting
futexes.  Any page with a futex waiting on it remains pinned in RAM,
which is a problem when many futexes are used, especially with FUTEX_FD.

Another problem is that the page is not always the correct one, if it
can be changed later by a COW (copy on write) operation.  This can
happen when waiting on a futex without writing to it after fork(),
exec() or mmap(), if the page is then written to before attempting to
wake a futex at the same adress. 

There are two symptoms of the COW problem:
 - The wrong process can receive wakeups
 - A process can fail to receive required wakeups. 

This patch fixes both by changing the indexing so that VM_SHARED
mappings use the triple (inode,offset,index), and private mappings use
the pair (mm,virtual_address).

The former correctly handles all shared mappings, including tmpfs and
therefore all kinds of shared memory (IPC shm, /dev/shm and
MAP_ANON|MAP_SHARED).  This works because every mapping which is
VM_SHARED has an associated non-zero vma->vm_file, and hence inode.
(This is ensured in do_mmap_pgoff, where it calls shmem_zero_setup). 

The latter handles all private mappings, both files and anonymous.  It
isn't affected by COW, because it doesn't care about the actual pages,
just the virtual address.

The patch has a few bonuses:

        1. It removes the vcache implementation, as only futexes were
           using it, and they don't any more.

        2. Removing the vcache should make COW page faults a bit faster.

        3. Futex operations no longer take the page table lock, walk
           the page table, fault in pages that aren't mapped in the
           page table, or do a vcache hash lookup - they are mostly a
           simple offset calculation with one hash for the futex
           table.  So they should be noticably faster.

Special thanks to Hugh Dickins, Andrew Morton and Rusty Russell for
insightful feedback.  All suggestions are included.

into home.osdl.org:/home/torvalds/v2.5/linux

From Matias Alejo Garcia <kernel@matiu.com.ar>.

MODULE_ALIAS_LDISC() is not in any way architecture-specific, so don't
put it in architecture header files.

Here's a patch which moves it to a more sensible location.

The "insert_here" list pointer logic was broken, and unnecessary. 

Kill it and its associated logic off completely - just tell the IO
scheduler what kind of insert it is.

This also makes the *_insert_request strategies much easier to follow,
imo.

into nuts.ninka.net:/disk1/davem/BK/net-2.5

Since sdla.c now has locking instead of cli/sti, it shouldn't be
completely busted on SMP.

Also, the frad interface registration needed to be done once
(and check the result), and undone on module unload.

* get rid of leftover sti
* no longer need MOD_INC/DEC stuff
* get rid of dead code related to MOD_INC/DEC
* use module_init/module_exit to cleanly run init code

into nuts.ninka.net:/disk1/davem/BK/net-2.5

try_then_request_module() does what crypto/autoload.c is doing, so
replace it.  Fix try_then_request_module(), too (thanks James).

I should have stayed in bed.

Apparently the new gcc 3.2.2 allows local variable declarations within
the code of a function if it is not used earlier. But older gcc's do
not allow this. 

into nuts.ninka.net:/disk1/davem/BK/net-2.5

Cleanup ikconfig
	- use single_open for built_with file.
	- get rid of unneeded globals
	- use copy_to_user instead of char at a time
	- only need the read routine, proc defaults to correct behaviour
	  for the rest.

When mmap MAP_SHARED is done on a file, it gets marked with VM_MAYSHARE
and, if it's read/write, VM_SHARED.  However, if it is remapped with
mremap(), the MAP_SHARED is only passed into the new mapping based on
VM_SHARED.  This means that remapped read only MAP_SHARED mappings lose
VM_MAYSHARE.  This is causing us a problem on parisc because we have to
align all shared mappings carefully to mitigate cache aliasing problems.

The fix is to key passing the MAP_SHARED flag back into the remapped are
off VM_MAYSHARE not VM_SHARED.

driver->supports_dma was used together with CONFIG_IDEDMA_ONLYDISK to limit
DMA access to disk devices only.  However Alan introduced new scheme in 2.5.63
and this field is not needed any longer because all ide drivers support DMA.