Patch from James Cleverdon & John Stultz

The IRQ balancing code currently assumes that the logical apicid is
always '1 << cpu', which is not true for the larger platforms.
We express this as an abstracted macro instead, and move the
cpu_to_logical_apicid definition to subarch, so we can make it exactly
"1 << cpu" for normal machines - maximum speed, minimum change risk.

A couple of things are abstracted from the smp_boot_cpus loop in order
to enable us to use the bios_cpu_apicid array to boot cpus from without
disturbing the code path of current machines.

Patch from James Cleverdon & John Stultz

This adds machine a type detection hook to the acpi code, and renames
raw_phys_apicid to bios_cpu_apicid (it's an array of apicid's to boot,
indexed by the bios' cpu numbering), and I other large machines will
need to use it later ... not necessarily using physical interrupts.

Patch from James Cleverdon & John Stultz

Currently the naming for the IO-APIC fields is very confused, we assign
dest_LowestPrio to delivery_mode, and INT_DELIVERY_MODE to dest_mode.
The values are correct, but the naming is wrong - this patch corrects
that confusion. It also moves the definitions of those settings into
subarch, where they belong (we have to use fixed delivery mode for Summit
due to what seems to be an Intel IO-APIC bug with P4 clustered mode).

The warning

	/lockd/clntXxXxXxXx RPC: Couldn't create pipefs entry

is due to the lockd process starting RPC clients as an unprivileged
user, causing path_walk() to fail.  The following patch fixes it.

I have more carefully tested the proposed removal of the NT flag
clearing on lcall entry.

The question I wanted to answer is: is it necessary to clear NT in the
sysenter entry path as implemented for lcall7/lcall27 or is it possible
to remove the flag manipulation from do_lcall?

Doing it only for one and not the other looks wrong since several return
paths are shared, especially the ones which end up in iret, the only
instruction which is affected by the NT flag.

The conclusion is that 2.5 is NT safe (had to dig out an old P5-133 which
I could crash without fear of data loss, so I have only tested on 1
machine). The reason this cleanup works is that now (since Jan 5th) flags
are saved and restored in switch_to() to keep IOPL private to a process
even when using sysenter/sysexit.

The side effect of that patch is that NT becomes also process-private
instead of infecting all processes and triggering a killfest of all user
mode processes, including init (AFAICT kernel threads survived, but I
did not have any debug tools enabled in the kernel).

The only addition to the preceding version is that interrupts are
reenabled in the iret fixup path because it seems that do_exit() might
otherwise spend quite some time with interrupts disabled.

New version with all ifdef CONFIG_MMU gone from procfs.

Instead, the conditional code is in either task_mmu.c/task_nommu.c, and
the Makefile will select the proper file for inclusion depending on
CONFIG_MMU.

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

This adds the new common m68knommu entry.S into the build list.

This converts the current m68knommu/68360 entry.S file to use the new
entry.h, and also removes all the common entry.S code that is now in the
common m68knommu/kernel/entry.S.

This converts the current m68knommu/68328 entry.S file to use the new
entry.h, and also removes all the common entry.S code that is now in the
common m68knommu/kernel/entry.S.

This converts the current m68knommu/5307 entry.S file to use the new
entry.h, and also removes all the common entry.S code that is now in the
common m68knommu/kernel/entry.S.

This overhauls asm-m68knommu/entry.h. It contains much cruft,
and is out of date relative to the underlying entry.S code.

More specifically this brings the SAVE_ALL and RESTORE_ALL macros
from the various m68knommu entry.S files into this header.

This cleans up the linker symbols used in the 68EZ328 ucdimm
target assembler head file. Removed some unused (and not defined)
names. Also changes a couple of names to be consistent with all
other m68knommu targets.

This cleans up the linker symbols used in the 68EZ328 ucsimm
target assembler head file. Removed some unused (and not defined)
names. Also changes a couple of names to be consistent with all
other m68knommu targets.

This removes the last remaining obsolete m68knommu sub-architecture
linker script. No longer needed with the new merge script.

This removes the BUG and PAGE_BUG macros from asm-m68knommu/page.h.
All this is now moved into asm-m68knommu/bug.h.

This adds the new bug.h file for the m68knommu arch.
It is basically a copy of asm-cris/bug.h.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

This patch has already made it into 2.4.21pre3-ac4. Please apply.

Actually exporting the symbol introduced in 2.5.57 makes module users
happy.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

The CPUFREQ initialisation now registers an interface with the device
model, and thus needs to initialise after postcore.  We use the
arch level for this.  This does, however, impose the restriction
that cpufreq may not be available for other architecture
initialisated code.

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

Remove ide_release_lock and ide_get_lock definitions from asm-arm/ide.h;
they're defined in include/linux/ide.h.

Add entries for sendfile64, futex, async io, etc system calls to
both unistd.h and the system call handler table.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

In addition to the diff from the 1.7 i8kutils release to the 1.13
release, I made the new globals static as per Rusty's namespace
pollution patch yesterday, and removed the reference to an include no
longer in 2.5.

	An old AMD 486DX4-SE(as reported by bios) here crashes on boot in
amd_init, doing rdmsr in k6 case. Elan fixes added case 4 there but
without break. This break allows it to boot.

Northwood P4's have one more bit in the CPUID processor info set: bit
31.  Intel calls the feature PBE (Pending Break Enable).

The attached patch adds the necessary entry.

Note, there are still races with unloading modules, this patch
does not fix that...

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

SGI Modid: 2.5.x-xfs:slinx:136827a