1. 03 Apr, 2003 2 commits
    • David Mosberger's avatar
      ia64: Checkin support files for vendor-specific ACPI extensions. · 8106c446
      David Mosberger authored
            Fix spelling of Hewlett-Packard.
      8106c446
    • Xavier Bru's avatar
      [PATCH] ia64: fix missing symbol exports · ce8a3d6e
      Xavier Bru authored
      3) with CONFIG_NUMA set, there are undefined symbols building modules:
      
      scripts/modpost vmlinux drivers/md/dm-mod.o drivers/net/e1000/e1000.o drivers/net/eepro100.o drivers/md/md.o drivers/net/mii.o fs/xfs/xfs.o
      *** Warning: cpu_info__per_cpu [fs/xfs/xfs.ko] undefined!
      *** Warning: cpu_info__per_cpu [drivers/md/md.ko] undefined!
      *** Warning: cpu_to_node_map [drivers/md/md.ko] undefined!
      
      exporting them in ia64_ksyms.c fixes the problem.
      ce8a3d6e
  2. 31 Mar, 2003 3 commits
  3. 27 Mar, 2003 6 commits
  4. 26 Mar, 2003 8 commits
  5. 25 Mar, 2003 1 commit
  6. 24 Mar, 2003 3 commits
    • Wolfgang Mauerer's avatar
      [PATCH] ia64: Cross-compile fix · 1bdbba7a
      Wolfgang Mauerer authored
      the attached patch (against bk-current) fixes a cross 
      compilation problem by using the target specific objdump 
      tool instead of the host specific one.
      1bdbba7a
    • David Mosberger's avatar
      ia64: Manual merge of Keith Owen's patch to avoid deadlock on · 07eac790
      David Mosberger authored
      	ia64_sal_mc_rendez().  Also prefix local-variables in
      	SAL macros to avoid name collisions.
      07eac790
    • Keith Owens's avatar
      [PATCH] ia64: mca rendezvous fix · 1794bb4e
      Keith Owens authored
      We are not setting the 'always rendezvous for mca' flag.  kdb needs it
      set to get decent mca debugging on all cpus but I do not want kdb to
      change sal behaviour.  Since we do not recover from mca without a
      debugger, I see no reason why this flag should not be on for all
      kernels.
      
      The rendezvous timeout was set to 100 * HZ, but SAL expects the timeout
      to be in milliseconds, HZ may not be 1 millisecond.  The patch makes
      the timeout an explicit 20 seconds, semi-arbitrary value.
      1794bb4e
  7. 21 Mar, 2003 3 commits
  8. 19 Mar, 2003 1 commit
    • Alex Williamson's avatar
      [PATCH] ia64: Use PAL_HALT_LIGHT in cpu_idle · 7691ec86
      Alex Williamson authored
      Here's patches for 2.4 & 2.5 to use PAL_HALT_LIGHT in cpu_idle.
      This helps to reduce CPU temp a little on boxes with firmware that
      takes advantage of this lower power state.  I've tried this on a
      rx2600 (2x900MHz McKinley) and an i2000 (fw 117) and it shows some
      benefit.  On McKinley systems, only the very latest PAL from Intel
      actually reduces power consumption in the halt_light state.  For HP
      rx2600/zx6000/zx2000, this means you need to be running firmware 1.82.
      
        Rohit Seth, at Intel, has run some benchmarks with this kind of
      modification and found the effects of enabling halt_light to fall
      within the noise of mosts tests.  I replaced pal_halt(1) in safe_halt
      with pal_halt_light() since halt_light is required to be implemented,
      but pal_halt(1) is an optional halt state.  I'd be interested to hear
      of any measurements anyone does using this, where it works/fails, and
      if any benchmarks/applications are impacted.
      7691ec86
  9. 18 Mar, 2003 4 commits
  10. 14 Mar, 2003 2 commits
  11. 13 Mar, 2003 3 commits
    • Eric Piel's avatar
      [PATCH] ia64: POSIX timer fixes · 2ffb1116
      Eric Piel authored
      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.
      2ffb1116
    • David Mosberger's avatar
      969c79c7
    • Jakub Jelínek's avatar
      [PATCH] ia64: clone2/clone argument order fixes · ebbece41
      Jakub Jelínek authored
      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).
      ebbece41
  12. 11 Mar, 2003 4 commits
    • David Mosberger's avatar
    • David Mosberger's avatar
      ia64: Remove ia64_spinlock_contention(). · 4760815e
      David Mosberger authored
      4760815e
    • Peter Chubb's avatar
      [PATCH] ia64: declare test_bit() arg as "const" · e21ab9c4
      Peter Chubb authored
      While you're fixing bitops.h, making test_bit take a const qualified
      arg will kill some warnings in reiserfs...
      e21ab9c4
    • Alex Williamson's avatar
      [PATCH] ia64: CPE & CMC polling for 2.5 · 26abebb8
      Alex Williamson authored
      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
      26abebb8