Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*CONFIG_FRAME_POINTER\s+and\s+arch\/i386\/kernel\/semaphore\.c\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*CONFIG_FRAME_POINTER\s+and\s+arch\/i386\/kernel\/semaphore\.c\s*$/: 14 ]

Total 14 documents matching your query.

1. CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: "John Hawkes" <hawkes@xxxxxxxxxxxx>; Date: Mon, 11 Dec 2000 09:33:34 -0800; Is there a reason why the xfs version of arch/i386/kernel/semaphore.c has added: ... for the asm routines __down_failed, __down_failed_interruptible, and __down_failed_trylock, but *not* for __up_wak; /archives/xfs/2000-12/msg00105.html (7,616 bytes)
2. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Russell Cattelan <cattelan@xxxxxxxxxxx>; Date: Mon, 11 Dec 2000 11:50:15 -0600; That is part of the KDB patch. It isn't specific to XFS.; /archives/xfs/2000-12/msg00106.html (8,236 bytes)
3. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Dec 2000 09:51:14 +1100; That is from the kdb patch, not from XFS. Unfortunately the use of CONFIG_FRAME_POINTER was added before I took over kdb so I am guessing here. Early versions of kdb required frame pointers to do bac; /archives/xfs/2000-12/msg00108.html (9,099 bytes)
4. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Rajagopal Ananthanarayanan <ananth@xxxxxxx>; Date: Mon, 11 Dec 2000 15:04:54 -0800; Yes, it is for backtracing purposes. I'd guess the two omitted routines were likely due to an oversight ... I know some of them were added because I had pointed out missing frames; guess there weren'; /archives/xfs/2000-12/msg00109.html (9,704 bytes)
5. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Dec 2000 10:17:06 +1100; gdb against the kernel needs frame pointers. kdb knows all about the kernel special cases on the stack, gdb does not. But since we have made a start on gdb over serial line to kdb, even that argument; /archives/xfs/2000-12/msg00111.html (8,390 bytes)
6. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: "John Hawkes" <hawkes@xxxxxxxxxxxx>; Date: Mon, 11 Dec 2000 17:09:53 -0800; As it turns out, kernprof's mcount functionality claims to need frame pointers (to the point where the high-level kernel Makefile turns on CONFIG_FRAME_POINTER if CONFIG_MCOUNT is set), yet the curre; /archives/xfs/2000-12/msg00113.html (8,585 bytes)
7. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Dec 2000 12:38:36 +1100; There have been claims in the past that mcount() gets the wrong return address on ix86 if frame pointers are not available. I tend to trust the people who made those claims but I could never reproduc; /archives/xfs/2000-12/msg00115.html (9,016 bytes)
8. CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: "John Hawkes" <hawkes@xxxxxxxxxxxx>; Date: Mon, 11 Dec 2000 09:33:34 -0800; Is there a reason why the xfs version of arch/i386/kernel/semaphore.c has added: ... for the asm routines __down_failed, __down_failed_interruptible, and __down_failed_trylock, but *not* for __up_wak; /archives/xfs/2000-12/msg00320.html (7,616 bytes)
9. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Russell Cattelan <cattelan@xxxxxxxxxxx>; Date: Mon, 11 Dec 2000 11:50:15 -0600; That is part of the KDB patch. It isn't specific to XFS.; /archives/xfs/2000-12/msg00321.html (8,236 bytes)
10. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Dec 2000 09:51:14 +1100; That is from the kdb patch, not from XFS. Unfortunately the use of CONFIG_FRAME_POINTER was added before I took over kdb so I am guessing here. Early versions of kdb required frame pointers to do bac; /archives/xfs/2000-12/msg00323.html (9,099 bytes)
11. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Rajagopal Ananthanarayanan <ananth@xxxxxxx>; Date: Mon, 11 Dec 2000 15:04:54 -0800; Yes, it is for backtracing purposes. I'd guess the two omitted routines were likely due to an oversight ... I know some of them were added because I had pointed out missing frames; guess there weren'; /archives/xfs/2000-12/msg00324.html (9,704 bytes)
12. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Dec 2000 10:17:06 +1100; gdb against the kernel needs frame pointers. kdb knows all about the kernel special cases on the stack, gdb does not. But since we have made a start on gdb over serial line to kdb, even that argument; /archives/xfs/2000-12/msg00326.html (8,390 bytes)
13. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: "John Hawkes" <hawkes@xxxxxxxxxxxx>; Date: Mon, 11 Dec 2000 17:09:53 -0800; As it turns out, kernprof's mcount functionality claims to need frame pointers (to the point where the high-level kernel Makefile turns on CONFIG_FRAME_POINTER if CONFIG_MCOUNT is set), yet the curre; /archives/xfs/2000-12/msg00328.html (8,585 bytes)
14. Re: CONFIG_FRAME_POINTER and arch/i386/kernel/semaphore.c (score: 1): Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>; Date: Tue, 12 Dec 2000 12:38:36 +1100; There have been claims in the past that mcount() gets the wrong return address on ix86 if frame pointers are not available. I tend to trust the people who made those claims but I could never reproduc; /archives/xfs/2000-12/msg00330.html (9,016 bytes)

Current List: 1 - 14
Page: [1]