1. 11 1月, 2006 1 次提交
  2. 07 1月, 2006 1 次提交
  3. 09 11月, 2005 1 次提交
  4. 31 10月, 2005 1 次提交
    • D
      [PATCH] fixup bogus e820 entry with mem= · f014a556
      Dave Hansen 提交于
      This was reported because someone was getting oopses reading /proc/iomem.
      It was tracked down to a zero-sized 'struct resource' entry which was
      located right at 4GB.
      
      You need two conditions to hit this bug: a BIOS E820_RAM area starting at
      exactly the boundary where you specify mem= (to get a zero-sized entry),
      and for the legacy_init_iomem_resources() loop to skip that resource (which
      only happens at exactly 4G).
      
      I think the killing zero-sized e820 entry is the easiest way to fix this.
      Signed-off-by: NDave Hansen <haveblue@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      f014a556
  5. 14 9月, 2005 1 次提交
  6. 13 9月, 2005 1 次提交
  7. 10 9月, 2005 2 次提交
  8. 08 9月, 2005 1 次提交
  9. 05 9月, 2005 2 次提交
  10. 25 8月, 2005 2 次提交
  11. 23 7月, 2005 1 次提交
    • L
      Remove "noreplacement" kernel command line option. · 72538d85
      Linus Torvalds 提交于
      It is no longer valid to not replace instructions, since we depend on
      different behaviour depending on CPU capabilities.
      
      If you need to limit the capabilities of the replacements (because the
      boot CPU has features that non-boot CPU's do not have, for example), you
      need to explicitly disable those capabilities that are not shared across
      all CPU's.
      
      For example, if your boot CPU has FXSR, but other CPU's in your system
      do not, you need to use the "nofxsr" kernel command line, not disable
      instruction replacement per se.
      72538d85
  12. 26 6月, 2005 6 次提交
  13. 24 6月, 2005 2 次提交
  14. 01 6月, 2005 1 次提交
  15. 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