From Matt Tolentino:

  Here's a small patch to change several data types from u64 to
  unsigned long in efi.h.  These changes enable the use of the
  same data structures and function prototypes for ia32 EFI kernels.

This applies on top of Takayoshi's interrupt polarity fix and just
makes things a tiny bit more consistent.

Is acpi_irq_to_vector() even needed anymore?  I don't see any
references to it.

The patch below removes the .weak symbol stuff from iosapic.c.

As far as I can tell, iosapic.c is compiled for every flavor except
the simulator.  I tried to boot the HP_SIM kernel on ski, but it
seems to loop in find_save_locs().  This happens both with and
without this patch, so maybe I have a local problem.  (I started
with a clean tree, did make

As in_atomic() uses kernel_locked() which is in smp_lock.h.

sn2 still doesn't use ACPI to describe PCI busses on the system (I'm
working on it), so we have to do it the old fashioned way.  This patch
also includes a few other fixes.

The attached patch (against 2.6) helps IA-32 applications take advantage of the
generic 32 bit (fs/compat_ioctl.c) ioctl handlers.

The patch was created by Matt Helsley <matthltc at us.ibm.com> for 2.4 and
has been changed slightly to match 2.6.

The implementation compromises performance for correctness.

Add include to fix compilation on x86-64

into home.osdl.org:/home/torvalds/v2.5/linux

Ack'd by Russell King as well.

The attached patch implements core dump functionality for IA-32
applications running on ia64.

We should amend that test for zombies to include the "dead" state as
well.

 Having necessary resources, I've decided to take over the maintenance of
the defxx driver for the PDQ-based family of DEC FDDI controllers (the
DEFEA for EISA and the DEFPA for PCI are the models currently handled).

I've talked to Larry, the original author and the last maintainer of the
code, and he's said he'd be happy about it.  He's asked me to update his
long-outdated contact information.

Here is a patch to update the driver to the PCI version of the DMA API.

The patch includes appropriate status and contact information updates.

into home.osdl.org:/home/torvalds/v2.5/linux

From Jay Estabrook <Jay.Estabrook@compaq.com>.

From Jay Estabrook <Jay.Estabrook@compaq.com>.

From Jay Estabrook <Jay.Estabrook@compaq.com>.

From: Nathan Scott <nathans@sgi.com>

XFS wants to use page->private as a bitmap of uptodate indicators for
sub-page-sized blocks (which is one of the things ->provate was intended
for).

But someone needs to initialise ->private somewhere.  best to do it in the
page allocator, so the zeroness of a new page's ->private becomes a
system-wide thing.

From: john stultz <johnstul@us.ibm.com>

I've found a race in the mtrr ipi_handler() and set_mtrr() functions.

Basically the server, set_mtrr() does the following:

  1.1 initialize a flag
  1.2 send ipi
  1.3 waits for all cpus to check in
  1.4 toggle flag
  1.5 do stuff
  1.6 wait for all cpus to check out
  1.7 toggle flag again
  1.8 return

While the clients, running ipi_handler() do the following:

  2.1 check in
  2.2 wait for flag
  2.3 do stuff
  2.4 check out
  2.5 wait for flag
  2.6 return

The problem is the flag is on the servers stack! So if 1.7 and 1.8
executes before 2.5 happens, the client's pointer to the flag becomes
invalid (likely overwritten) which causes the client to never see the
flag change, hanging the box.

The patch fixes that by adding a final synchronisation step in which the
controlling CPU waits for all the IPI'ed CPUs to complete.

From: Martin Pool <mbp@samba.org>

ia64_mv_irq_desc returns a 'struct irq_desc', which had a forward declaration
but did not actually exist.  We're currently using a silly anonymous struct
typedefed to irq_desc_t.

Now add the structure name as well.

Teach journal_get_write_access() and journal_get_undo_access() to handle
aborted trasaction handles.

From: george anzinger <george@mvista.com>

a) Fixes bug 858 (http://bugme.osdl.org/show_bug.cgi?id=858)

   The problem was caused by round off error in calculating the correct
   jiffies value in micro seconds to do the round up to jiffies.  The fix
   is to do the round up AFTER conversion to jiffies, rather than before.
   This only affected the timeval to jiffies calculation.

b) Changed the scale values to get the highest possible precision short
   of going to full 64-bit math.  This is particularly useful in the
   scaling of the seconds part of time.  The code now computes a trial
   value at compile time and adjusts the scaling if the result is less than
   32 bits.

c) Adds comments to time.h to remove (I hope) ALL the confusion that
   this file use to generate.

From: Peter Chubb <peterc@gelato.unsw.edu.au>

Currently, do_setitimer() is used in several files, but doesn't appear
in any header.  Thus its declaration is repeated in some files, and
its use causes a warning in others (because there is no declaration
present).

This patch:
     -- adds a couple of declarations to linux/times.h
     -- removes the (now duplicate) declarations from other files.

From: Ville Herva <vherva@niksula.hut.fi>

NMI watchdog is nowadays supported on x86-64, too. The nmi-watchdog.txt
document doesn't mention this. Here is a patch to add a few words on that.

From: jbarnes@sgi.com (Jesse Barnes)

Currently, free_all_bootmem_core() assumes that the bdata for a given
node will begin where the node's memory map begins.  This isn't
necessarily true on machines that use a virtual memory map (e.g. ia64
discontig machines), so we fix page to point to the first actual page of
RAM on the node, which _does_ contain the bdata struct.

From: jbarnes@sgi.com (Jesse Barnes)

hwgfs needs lookup_create(), and intermezzo already has copied it.

Document it, export it to modules and fix intermezzo.

From: Andi Kleen <ak@muc.de>

In some cases panic can be called with interrupts off.  Don't trigger the
NMI watchdog in this case when a panic= parameter is specified.

From: Matt Mackall <mpm@selenic.com>

This only checks in the non-__ versions, as those are occassionally
called inside things like kmap_atomic pairs which take a spinlock in
with highmem. It's all conditional on CONFIG_DEBUG_SPINLOCK_SLEEP
(which isn't quite the right name) so there's no overhead for normal
builds.

cdrom_decode_status() can call cdrom_end_request() twice.  The second call
oopses because the first call destroyed the request.

Fix it to only call cdrom_end_request() once.

Jens has acked this change.