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.

  (show_min_state): Fix typo r11 -> r12.

into tiger.hpl.hp.com:/data1/bk/lia64/to-linus-2.5

Here are two fixes for the ia32-compatibility mode handling
for the new semtimedop() system call for the ia64 architecture.

The first problem was that treatment of user-mode calls to semtimedop()
with a NULL 4th (struct timespec *) parameter was inconsistent with the
behavior of the same executable on i386 and also with a natively compiled
ia64 binary.  A NULL 4th arg to semtimedop() should result in no timeout
being used (like a straight semop() call) rather than in an EFAULT error.

The second problem was that a legitimate semtimedop() with a timeout was
also resulting in an EFAULT because the fetch of the internal timespec
strucure by sys_semtimedop() from semtimedop32()'s kernel stack was
treated as an invalid user-data reference.  This requires temporarily
switching the addressing limit with set_fs(), further requiring that
appropriate parameter checking by performed prior to the switch.

The const qualifier was removed from the (struct compat_timespec *) arg
to semtimedop32() so that the call to get_compat_timespec() wouldn't
generate a compilation warning.

This is to

  - handle _CRS with multiple vendor-specific resources
  - use acpi_walk_resources() instead of doing it by hand
  - make lookup of vendor resource by GUID generic
  - cleanup now-unused helper functions

(This depends on the previous IO port space patches, because
they removed the last of acpi_get_addr_space()).

My hope is that acpi_vendor_resource_match() and
acpi_find_vendor_resource() can someday move into ACPI,
but that probably depends on getting the idea of labelling
vendor resources with a GUID into the spec.  HP does this
and I think is working on putting it in the spec.