An error occurred fetching the project authors.
  1. 26 Sep, 2006 1 commit
  2. 31 Mar, 2006 3 commits
  3. 19 Jan, 2006 2 commits
  4. 12 Jan, 2006 1 commit
  5. 09 Jan, 2006 1 commit
  6. 06 Jan, 2006 1 commit
    • Jeff Dike's avatar
      [PATCH] uml: separate libc-dependent umid code · 2264c475
      Jeff Dike authored
      I reworked Gennady's umid OS abstraction patch because the code shouldn't
      be moved entirely to os.  As it turns out, I moved most of it anyway.  This
      patch is the minimal one needed to move the code and have it work.
      It turns out that the concept of the umid is OS-independent, but
      almost everything else about the implementation is OS-dependent.
      
      This is code movement without cleanup - a follow-on patch tidies
      everything up without shuffling code around.
      Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
      Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      2264c475
  7. 30 Oct, 2005 1 commit
  8. 28 Oct, 2005 1 commit
  9. 23 Sep, 2005 1 commit
  10. 17 Sep, 2005 2 commits
    • Jeff Dike's avatar
      [PATCH] uml: breakpoint an arbitrary thread · 3eddddcf
      Jeff Dike authored
      This patch implements a stack trace for a thread, not unlike sysrq-t does.
      The advantage to this is that a break point can be placed on showreqs, so that
      upon showing the stack, you jump immediately into the debugger.  While sysrq-t
      does the same thing, sysrq-t shows *all* threads stacks.  It also doesn't work
      right now.  In the future, I thought it might be acceptable to make this show
      all pids stacks, but perhaps leaving well enough alone and just using sysrq-t
      would be okay.  For now, upon receiving the stack command, UML switches
      context to that thread, dumps its registers, and then switches context back to
      the original thread.  Since UML compacts all threads into one of 4 host
      threads, this sort of mechanism could be expanded in the future to include
      other debugging helpers that sysrq does not cover.
      
      Note by jdike - The main benefit to this is that it brings an arbitrary thread
      back into context, where it can be examined by gdb.  The fact that it dumps it
      stack is secondary.  This provides the capability to examine a sleeping
      thread, which has existed in tt mode, but not in skas mode until now.
      
      Also, the other threads, that sysrq doesn't cover, can be gdb-ed directly
      anyway.
      
      Signed-off-by: Allan Graves<allan.graves@gmail.com>
      Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
      Cc: Paolo Giarrusso <blaisorblade@yahoo.it>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      3eddddcf
    • Jeff Dike's avatar
      [PATCH] uml: _switch_to code consolidation · f6e34c6a
      Jeff Dike authored
      This patch moves code that is in both switch_to_tt and switch_to_skas to the
      top level _switch_to function, keeping us from duplicating code.  It is
      required for the stack trace patch to work properly.
      Signed-off-by: default avatarAllan Graves <allan.graves@gmail.com>
      Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
      Cc: Paolo Giarrusso <blaisorblade@yahoo.it>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      f6e34c6a
  11. 29 Jul, 2005 1 commit
  12. 25 Jun, 2005 2 commits
  13. 23 Jun, 2005 1 commit
  14. 28 May, 2005 2 commits
  15. 07 May, 2005 3 commits
  16. 01 May, 2005 1 commit
  17. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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