Patch by Rohit Seth, Fengua Yu, and Arun Sharma:

Please find attached a patch for kernel entry exit optimization. This is
based on 2.5.69 kernel.

The main items covered by this patch are:
1) Support for 16 bytes instructions as per SDM2.1 (CSD/SSD in pt_regs)
2) f10-f11 are added as additional scratch registers for kernel's use.
3) Re-arrange pt_regs to access less cache lines in system call. Reduce
scratch register saving/restoring in system call path.
4) A few instruction reorg in low-level code.

	came out wrong.

Some patches from hch@infradead.org cleaning up sn2 code a bit,
including the removal of some unnecessary files.

This patch moves the kernel text and data into region 5 (0xa00...) by using
a translation register to pin the entire area (i.e., no TLB faults).
The 1st-order goal is to be able to boot a kernel even when there is
no usable memory in the 64-128MB range.  It is also a step towards enabling
text-replication on NUMA.

This patch allows users to set the PMC to their default value, even
though the value might conflict with the type of monitoring
session. This is fine because default values ensure the monitor is not
active.

      callbacks so last_nsec_offset gets updated, too.

	so it handles not-present translations for region 5 (patch by John Marvin).

      changes by yours truly.

is INT_MAX and the value of size for n = INT_MAX is 268435456. So I don't think
there'll be an overflow.

Make it possible to plug in alternate time-offset sources, such as external
(e.g., chipset) timers or High-Performance Event Timer (HPET) etc. This
is needed on platforms where the cycle-counters on different CPUs may
drift apart from each other.
This patch contains the ia64-specific portion only.

	kernel if CONFIG_MD_RAID5 is declared.

Attached is the updated patch that takes the supported purge page size
bits from PAL call.

This is a fix to kernel_thread(). I dont claim to fix any real problem
its just a fix to return pid_t. This is part of a series of fixes for
the linux kernel 2.4.20 to make proper use of pid_t.

Please find attached a small update that syncs up the definition and
usage of check_valid_hugepage_range across different arch dependent and
independent files.

	wasn't updated and one place in the sigreturn path where
	the fph-owner wasn't set.