1. 16 1月, 2008 1 次提交
    • L
      [IA64] Fix unaligned handler for floating point instructions with base update · 1a499150
      Luck, Tony 提交于
      The compiler team did the hard work for this distilling a problem in
      large fortran application which showed up when applied to a 290MB input
      data set down to this instruction:
      
      	ldfd f34=[r17],-8
      
      Which they noticed incremented r17 by 0x10 rather than decrementing it
      by 8 when the value in r17 caused an unaligned data fault.  I tracked
      it down to some bad instruction decoding in unaligned.c. The code
      assumes that the 'x' bit can determine whether the instruction is
      an "ldf" or "ldfp" ... which it is for opcode=6 (see table 4-29 on
      page 3:302 of the SDM).  But for opcode=7 the 'x' bit is irrelevent,
      all variants are "ldf" instructions (see table 4-36 on page 3:306).
      
      Note also that interpreting the instruction as "ldfp" means that the
      "paired" floating point register (f35 in the example here) will also
      be corrupted.
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      1a499150
  2. 20 10月, 2007 1 次提交
  3. 09 5月, 2007 1 次提交
  4. 01 3月, 2006 1 次提交
  5. 28 2月, 2006 1 次提交
    • T
      [IA64] die_if_kernel() can return · e963701a
      Tony Luck 提交于
      arch/ia64/kernel/unaligned.c erroneously marked die_if_kernel()
      with a "noreturn" attribute ... which is silly (it returns whenever
      the argument regs say that the fault happened in user mode, as one
      might expect given the "if_kernel" part of its name!).  Thanks to
      Alan and Gareth for pointing this out.
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      e963701a
  6. 25 1月, 2006 1 次提交
  7. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4