1. 16 10月, 2008 3 次提交
  2. 30 1月, 2008 4 次提交
  3. 20 10月, 2007 2 次提交
  4. 11 10月, 2007 1 次提交
  5. 15 2月, 2006 1 次提交
    • G
      [PATCH] x86: fix oprofile kernel callgraph regression · 30379440
      Gerald Britton 提交于
      Fix x86 oprofile regression introduced by:
        commit c34d1b4d
        [PATCH] mm: kill check_user_page_readable
      
      That commit reorganized tests for the userspace stack walking moving all
      those tests into dump_backtrace(), however, dump_backtrace() was used for
      both userspace and kernel stalk walking.  The result is typically no
      recorded callgraph information for kernel samples.
      
      Revive the original function as dump_kernel_backtrace() and rename the
      other to dump_user_backtrace() to avoid future confusion.
      Signed-off-by: NGerald Britton <gbritton@alum.mit.edu>
      Apology-from: Hugh Dickins <hugh@veritas.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      30379440
  6. 04 2月, 2006 1 次提交
    • T
      [PATCH] OProfile: fixed x86_64 incorrect kernel call graphs · 23332c2e
      Tong Li 提交于
      Fix the problem in kernel 2.6.15.1 (and early versions) that OProfile on
      x86_64 does not correctly collect the stack traces for kernel functions.
      
      The original code in valid_kernel_stack() in arch/i386/oprofile/backtrace.c
      assumes that the frame pointer (headaddr) should be greater than stack
      (i.e., regs).
      
      This assumption is wrong for x86_64 because NMIs in x86_64 use a seperate
      stack different from the kernel stack.  Therefore, the variable stack now
      points to some location on the NMI stack, which turns out to be at a higher
      address than the frame pointer (headaddr) on the kernel stack.  The correct
      comparison here should be between headaddr and regs->rsp for x86_64.
      Signed-off-by: NTong Li <tong.n.li@intel.com>
      Cc: John Levon <levon@movementarian.org>
      Cc: Philippe Elie <phil.el@wanadoo.fr>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      23332c2e
  7. 30 10月, 2005 1 次提交
    • H
      [PATCH] mm: kill check_user_page_readable · c34d1b4d
      Hugh Dickins 提交于
      check_user_page_readable is a problematic variant of follow_page.  It's used
      only by oprofile's i386 and arm backtrace code, at interrupt time, to
      establish whether a userspace stackframe is currently readable.
      
      This is problematic, because we want to push the page_table_lock down inside
      follow_page, and later split it; whereas oprofile is doing a spin_trylock on
      it (in the i386 case, forgotten in the arm case), and needs that to pin
      perhaps two pages spanned by the stackframe (which might be covered by
      different locks when we split).
      
      I think oprofile is going about this in the wrong way: it doesn't need to know
      the area is readable (neither i386 nor arm uses read protection of user
      pages), it doesn't need to pin the memory, it should simply
      __copy_from_user_inatomic, and see if that succeeds or not.  Sorry, but I've
      not got around to devising the sparse __user annotations for this.
      
      Then we can eliminate check_user_page_readable, and return to a single
      follow_page without the __follow_page variants.
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      c34d1b4d
  8. 24 6月, 2005 1 次提交
  9. 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