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.

This is a trivial patch that makes sba_iommu recognize a new IOC.
Only change is that it will print

    IOC: sx1000 0.1 HPA 0xf8120002000 IOVA space 1024Mb at 0x80000000

instead of

    IOC: Unknown (103c:127c) 0.1 HPA 0xf8120002000 IOVA space 1024Mb
at 0x80000000

trivial (whitespace, copyright, and move pcibios_fixup_device_resources
closer to related code)

add support for /proc/iomem and /proc/ioports

enhance pcibios_scan_root to get multiple mem & io windows from ACPI _CRS,
and fixup all the resources

This has been in my 2.4 BK tree for a while, but I should have
posted it in case there's feedback from other people working
on large machines.  So here it is, in four parts:

  1  enhance __ia64_mk_io_addr(port)
  2  enhance pcibios_scan_root to get multiple mem & io windows
      from ACPI _CRS, and fixup all the resources
  3  add support for /proc/iomem and /proc/ioports
  4  trivial (whitespace, copyright, and move pcibios_fixup_device_resources
       closer to related code)

The current scheme is that IO ports are 64 bits, with the low 24
bits being the port number within an IO port space, and the upper
bits identifying the space.  There is currently a limit of 16
spaces.

Here's some cleanups/fixes/changes for interrupts on 2.5.67 + ia64.
Specifically:

  - Cleanup some ugliness with polarity/trigger setup.

  - Add iosapic_enable_intr() to set_rte on an interupt when the
    device is enabled.  IMHO, we really only want to unmask RTEs
    for PRTs we might actually use.  This moves the interrupt
    distribution here too.

  - When changing a vector from edge to level, call register_intr()
    to do it so all the data structures get set correctly.  If we
    have to guess how to setup an interupt and get it wrong, this
    should close some holes in changing it back to the correct type.

  - Register the HCDP interrupt in 8250_hcdp - this is where we have
    to guess the polarity/trigger.  The real handler will get fixed
    up via PCI setup or ACPI namespace serial support, this gets it
    associated w/ the port at setup.  This should allow interrupts
    to work when using builtin UARTs as console on HP Itanium2 boxes.

This patch fixes the issue of some CPUs not showing timer interrupts
going off.  Seems during the process of sync'ing the itc, we jumped over
the next timer value.  This patch is against 2.5.67 + ia64.  I haven't
seen the problem on 2.4, but a quick looks seems like it's potentially
an issue there too.

Please apply the following patch on top of 2.5.6x. This patch does the
following:

- repair broken system-wide overflow notification
- repair broken per-process notification
- fix a problem in the resrved bitmask for opcode 
  matcher8,9 for McKinley as reported by UIUC.
- forcing of bit2 for pmc8/pmc9 now part of reserved bitmask
- add the unsecure option to perfmon
- update to perfmon 1.4 (similar to 2.4)