should not use such innocent variable names like tmp because they
have a high probability to clash with (part of) the argument.

The patch allows unw_access_gr() to read from r0, to support unwind
directives such as .save ar.pfs,r0 and .save rp,r0.

Here is a patch to have the POSIX timer interface completly integrated
in ia64 (2.5.64). The programs in userland can now access the siginfo
structure. With that patch the test programs of the high resolution
timers pass without error but one which seems to also be triggered on
ix86: nanosleeps too short.

do_fork is declared as:
struct task_struct *do_fork(unsigned long clone_flags,
                            unsigned long stack_start,
                            struct pt_regs *regs,
                            unsigned long stack_size,
                            int *parent_tidptr,
                            int *child_tidptr)
ie. parent_tidptr is out4 and child_tidptr is out5, but
the comments in clone2 were suggesting otherwise.
So, we either need a patch which will codify current order
of clone arguments (ie. ptid, ctid, tls; attached below - has the advantage
that clone2 stays with the same ABI as in 2.5.[56]x), or the arguments
of clone2 and clone should be reordered to match the IA-32 order
(which is ptid, tls, ctid).

While you're fixing bitops.h, making test_bit take a const qualified
arg will kill some warnings in reiserfs...

Here's another feature I'd like to add to MCA support; the ability
to detect a flood of CMCs and switch to polling mode for retrieving
CMC logs.  Once no more CMC logs are found, return to and interrupt
driven handler.  If the flood threshold is never reached, the CMC
handler simply behaves as it does today.

   It's useful to get the CMC logs to know that something isn't
quite right, but if you end up with some bad memory it's too easy for
them to interfere with useful work.  I've tested this on an HP rx2600,
with a known bad DIMM.  This DIMM acts like it has a completely dead
DRAM on it.  With the current CMC handler, once I hit that range of
memory addresses, the system essentially dies, constantly handling
CMC errors.  With this patch, the system hits the threshold quickly,
but remains functional with no performance degredation once in polling
mode.  This patch applies against linux-2.4.20-ia64-021210 and 
includes:

 - Switching CMCs to polling mode at predeterimined threshold
 - If polling for CPEs, poll on all processors
 - Fix timestamp on log output

	in kernel unwinder.

Make CONFIG_SYSCTL control sys32_sysctl as well.  Based on a patch from Peter Chubb.

Andy Grover told me this should be posted here.  It allows ACPI to
compile even with PCI turned off.  Patch against 2.5.60.

ia 64 part of the patch.  This gives you a 32 bit version of sys_futex (hopefully).

	triggered by NaT-page-consumption faults.

	can be optimized properly.

	ensure that PCI line-size gets programmed properly.  Based
	on patch by Grant Grundler.

	Keith Owens.

Latest premption patch.

Please find attached a small hugetlb page support update for 2.5.60
IA-64 kernel (+ my previous hugetlb page patch).  This patch adds the
HAVE_ARCH_HUGETLB_UNMAPPED_AREA define for IA-64 arch.
hugetlb_get_unmapped_area function is added in
arch/ia64/mm/hugetlbpage.c

Please find attached a hugetlb page patch for IA-64 2.5.60 kernel .
Changes in generic files are mostly backported from 2.5.62 (to get
hugetlb support functioning properly).

 - Cleanup Makefile.
 - Fix potentional crash in dv1394 module unload.
 - Why does ARM's memcpy not return void*? Oh well, work around it in
  eth1394 by not expecting standard behavior.

And here's the SN specific part of the update.  This should get an SN2
compile all the way to the link stage, where I still have some devfs
stuff to cleanup.

Here's an update to the ia64 mmzone.h file that adds some SN2 specific
defines (which will probably have to be changed later, but it's a
start).

IA64 ABI specifies that globals > 8 bytes need to be aligned to 16 bytes.
gcc doesn't follow this convention. Current kernel code will fail to work with
a compiler which follows the ABI.

size of structure ia64_machine_vector is > 8 bytes and not multiple of 16 bytes.
When we have CONFIG_IA64_GENERIC, each machine specific vector from different
object files gets linked into a user defined section(forming array of
structures).

Now with a compiler conforming to ABI, there will be holes in this array
resulting in the code failure when it goes through this array of structures.

Following patch will make the size of the structure to be multiple of 16 bytes
making both ABI confirming/non-conforming compilers happy.

Current 2.5 kernels are broken with CONFIG_IA64_GENERIC option. Two unused
members are still remaining in the structure, resulting in corruption of
structure elements during the MACHVEC_INIT initialization. Attached patch
fixes this problem.

Rationalize __init/__devinit attributes.  The noteworthy changes are
that
iosapic_system_init(),
iosapic_init(),
iosapic_register_platform_intr(), and
iosapic_override_isa_irq()
are __init (only called from ACPI __init functions), but
iosapic_lists[],
num_iosapic,
find_iosapic(),
register_intr(),
iosapic_register_intr(), and
acpi_register_irq()
are not because they may be used after init-time by modules.

More detailed analysis:

        iosapic_lists[], num_iosapic: normal, referenced by
                find_iosapic (normal)
                register_intr (normal)
                iosapic_init (__init)

        pcat_compat: __initdata, referenced by
                iosapic_system_init (__init)
                iosapic_init (__init)
                iosapic_parse_prt (__init)

        find_iosapic: normal, called by
                register_intr (normal)

        register_intr: normal, called by
                iosapic_register_intr (normal), called by
                        acpi_register_irq (normal), called by
                                modules (=> can't be __init or __devinit)
                iosapic_register_platform_intr (__init)
                iosapic_override_isa_irq (__init)
                iosapic_parse_prt (__init)

        iosapic_reassign_vector: __init, called by
                iosapic_register_platform_intr (__init), called by
                        acpi_parse_plat_int_src (__init)

        iosapic_system_init: __init, called by
                acpi_parse_madt (__init)

        iosapic_init: __init, called by
                acpi_parse_iosapic (__init)

        iosapic_register_platform_intr: __init, called by
                acpi_parse_plat_int_src (__init)

        iosapic_override_isa_irq: __init, called by
                acpi_parse_int_src_ovr (__init)
                iosapic_init (__init)

        fixup_vector: __init, called by
                iosapic_parse_prt (__init), called by
                        acpi_pci_irq_init (__init)

Make interrupt registration functions take named constants for
polarity and trigger mode.  Old -> new magic decoder ring:
polarity 0 -> IOSAPIC_POL_LOW(#defined to 1)
polarity 1 -> IOSAPIC_POL_HIGH(#defined to 0)
trigger 0  -> IOSAPIC_LEVEL(#defined to 1)
trigger 1  -> IOSAPIC_EDGE(#defined to 0)

Simplify ISA IRQ init by taking advantage of iosapic_override_isa_irq(),
which already does what we need.

emove IOSAPIC address and GSI base from external interrupt
registration interfaces.  This lets us remove acpi_find_iosapic(),
which is functionally similar to find_iosapic().