On some machines that support I/O hot-plugging,
it happens that after boottime one or more IO SAPICs appear
after hot-plug event.  Even in that case, ACPI _PRT entries
can exist for devices behind those IO SAPICs at boottime
for future use.

Currently iosapic.c will give up parsing _PRT entries
once one of them hits such a non-existent IO SAPIC.

This patch fixes the problem on 2.5 ia64 bk tree.
For 2.4, we don't have this problem now.

Here is the patch. It is rather big because there is some renaming and
cleanups.  This patch bring 2.5 in line with 2.4.20: perfmon-1.3

It adds:
        - idle task exclusion
        - less ctxsw overhead in system wide
        - cleanups most of the inline asm
        - don't use PAL anymore to determine PMU features
        - added temporary hooks for custom overflow handlers (VTUNE/Oprofile)
        - renaming of the perfmon init functions

Thanks.

Please find attached a patch that brings in the support of hugetlb
inline with the ia32 tree.  This removes the syscall interface and gets
the hugetlbfs support (using mmap and shmat).  I might be sending you
couple of more small updates a little later.  At least wanted to get
this out first.

	in the tools directory.  Patch by Yu, Fenghua.

Cleanup the irq handling macros.

	the unwind info for consistency (well, just the obvious
	stuff, but it's a start).
	Fix the couple of bugs that this script uncovered (and work
	around one false positive).

	Reported by Dan Magenheimer (note: the bug didn't affect
	the existing kernel, since the possible values passed to
	the routine were always "safe").

	Add workaround for McKinley Erratum 7.

	accelerate normal system calls, but it puts the infrastructure in place
	and lets you write fsyscall-handlers to your hearts content.  A null system-
	call (such as getpid()) can now run in as little as 35 cycles!

	etc.

into home.transmeta.com:/home/torvalds/v2.5/linux

The linear target was getting the start sector wrong when doing a
dm_get_device(). [Kevin Corry]

The block layer does not honour bio->bi_size when issuing io, instead
it performs io to the complete bvecs.  This means we have to change
the bio splitting code slightly.

Given a bio we repeatedly apply one of the following three operations
until there is no more io left in the bio:

1) The remaining io does not cross an io/target boundary, so just
   create a clone and issue all of the io.

2) There are some bvecs at the start of the bio that are not split by
   a target boundary.  Create a clone for these bvecs only.

3) The first bvec needs splitting, use bio_alloc() to create *two*
   bios, one for the first half of the bvec, the other for the second
   half.  A bvec can never contain more than one boundary.

o  If there's an error you still need to call bio_endio with bio->bi_size
   as the 'done' param.

o  Simplify clone_endio.

[Kevin Corry]

Remove verbose debug message 'Splitting page'.

Remove some paranoia in highmem.c

Some fields in the duplicated bio weren't being set up properly in
__split_page(). [Kevin Corry]

md->pending was being incremented for each clone rather than just
once. [Kevin Corry]

dec_pending(): only bother spin locking if io->error is going to be
updated. [Kevin Corry]

Add a blk_run_queues() call to encourage pending io to flush
when we're doing a dm_suspend().

dm_suspend(): Stop holding the read lock around the while loop that
waits for pending io to complete.

queue_io() was checking the DMF_SUSPENDED flag rather than the new
DMF_BLOCK_IO flag.  This meant suspend could deadlock under load.

Give each device its own io mempool to avoid a potential
deadlock with stacked devices.  [HM + EJT]

There's a bug in the dm-stripe.c constructor failing top check if enough
destinations are handed in. [Heinz Mauelshagen]

minor change for dm-stripe.c. Tests for correct chunksize before it allocates
the stripe context. [Heinz Mauelshagen]

check_device_area was comparing the bytes with sectors.
[Stefan Lauterbach]

No need to validate the parameters if we are doing a
REMOVE_ALL command.

Return -ENOTBLK if lookup_device() finds the inode, but it
is not a block device. [Cristoph Hellwig]