[PATCH] RUSAGE_THREAD

2008-02-04 Thread Sripathi Kodi
option for the getrusage system call. Signed-off-by: Roland McGrath <[EMAIL PROTECTED]> Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> --- include/linux/resource.h |1 + kernel/sys.c | 31 ++- 2 files changed, 23 insertions(+), 9 deletions(-)

[PATCH] RUSAGE_THREAD

2008-02-04 Thread Sripathi Kodi
option for the getrusage system call. Signed-off-by: Roland McGrath [EMAIL PROTECTED] Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] --- include/linux/resource.h |1 + kernel/sys.c | 31 ++- 2 files changed, 23 insertions(+), 9 deletions(-) diff -uprN

Re: [RFC] Per-thread getrusage

2008-01-28 Thread Sripathi Kodi
Hi Andrew, On Monday 28 January 2008 11:22, Andrew Morton wrote: > On Thu, 17 Jan 2008 13:57:05 +0530 Vinay Sridhar <[EMAIL PROTECTED]> wrote: > > Hi All, > > > > Last year, there was discussion about per-thread getrusage by > > adding RUSAGE_THREAD flag to getrusage(). Please refer to the

Re: [RFC] Per-thread getrusage

2008-01-28 Thread Sripathi Kodi
Hi Andrew, On Monday 28 January 2008 11:22, Andrew Morton wrote: On Thu, 17 Jan 2008 13:57:05 +0530 Vinay Sridhar [EMAIL PROTECTED] wrote: Hi All, Last year, there was discussion about per-thread getrusage by adding RUSAGE_THREAD flag to getrusage(). Please refer to the thread

[ppc] Disparity between sys_clock_getres and vdso implementation

2008-01-27 Thread Sripathi Kodi
Hi Paul, On PPC, I see a disparity between clock_getres implementations in the vdso and syscall. I am using a IBM Openpower hardware and 2.6.24 kernel with CONFIG_HIGH_RES_TIMERS=y. clock_getres call for CLOCK_REALTIME returns 1 millisecond. However, when I edit

[ppc] Disparity between sys_clock_getres and vdso implementation

2008-01-27 Thread Sripathi Kodi
Hi Paul, On PPC, I see a disparity between clock_getres implementations in the vdso and syscall. I am using a IBM Openpower hardware and 2.6.24 kernel with CONFIG_HIGH_RES_TIMERS=y. clock_getres call for CLOCK_REALTIME returns 1 millisecond. However, when I edit

[PATCH PREEMPT_RT] Compilation fix for PPC

2008-01-12 Thread Sripathi Kodi
: error: invalid lvalue in unary ‘&’ The patch below fixes it. Thanks, Sripathi. Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> diff -uprN linux-2.6.24-rc5-rt1_org/include/asm-powerpc/percpu.h linux-2.6.24-rc5-rt1/include/asm-powerpc/percpu.h --- linux-2.6.24-rc5-rt1_org/include/as

[PATCH PREEMPT_RT] Compilation fix for PPC

2008-01-12 Thread Sripathi Kodi
below fixes it. Thanks, Sripathi. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] diff -uprN linux-2.6.24-rc5-rt1_org/include/asm-powerpc/percpu.h linux-2.6.24-rc5-rt1/include/asm-powerpc/percpu.h --- linux-2.6.24-rc5-rt1_org/include/asm-powerpc/percpu.h 2008-01-12 17:43:03.0 +0530

[PREEMPT_RT] LOCK_STAT and kexec: general protection fault

2007-11-20 Thread Sripathi Kodi
Hi, On RT kernel, When CONFIG_LOCK_STAT is enabled, trying to load the kdump kernel (kexec -p) causes a kernel panic. I have seen slightly varying backtraces, but I see general protection fault every time. Hardware: x86_64, 4CPUs, LS20 blade. Kernel: 2.6.23.1-rt11. I don't see this problem on

[PREEMPT_RT] LOCK_STAT and kexec: general protection fault

2007-11-20 Thread Sripathi Kodi
Hi, On RT kernel, When CONFIG_LOCK_STAT is enabled, trying to load the kdump kernel (kexec -p) causes a kernel panic. I have seen slightly varying backtraces, but I see general protection fault every time. Hardware: x86_64, 4CPUs, LS20 blade. Kernel: 2.6.23.1-rt11. I don't see this problem on

Re: [PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-10 Thread Sripathi Kodi
Hi Andrew, On Thursday 10 May 2007 07:20, you wrote: > On Wed, 9 May 2007 14:13:27 +0530 Sripathi Kodi <[EMAIL PROTECTED]> wrote: > Your changelogs aren't vey logical. The context for this change is off in > > a different patch. I reproduce it here: > > I am

[PREEMPT_RT] [PATCH 1/2] Introduce write_trylock_irqsave

2007-05-10 Thread Sripathi Kodi
remain disabled. I have also sent patches for mainline kernel. Please refer http://lkml.org/lkml/2007/05/09/76 , http://lkml.org/lkml/2007/05/09/79 and http://lkml.org/lkml/2007/05/09/550 This patch adds write_trylock_irqsave function. Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> Index:

[PREEMPT_RT] [PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-10 Thread Sripathi Kodi
Hi Ingo, This patch makes ptrace_attach() use the new API write_trylock_irqsave(). With this, the code in ptrace_attach() will be same for mainline and -rt. On -rt, write_trylock_irqsave() doesn't disable irqs and hence the problem is avoided. Signed-off-by: Sripathi Kodi <[EMAIL PROTEC

[PREEMPT_RT] [PATCH 1/2] Introduce write_trylock_irqsave

2007-05-10 Thread Sripathi Kodi
remain disabled. I have also sent patches for mainline kernel. Please refer http://lkml.org/lkml/2007/05/09/76 , http://lkml.org/lkml/2007/05/09/79 and http://lkml.org/lkml/2007/05/09/550 This patch adds write_trylock_irqsave function. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] Index: linux

[PREEMPT_RT] [PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-10 Thread Sripathi Kodi
Hi Ingo, This patch makes ptrace_attach() use the new API write_trylock_irqsave(). With this, the code in ptrace_attach() will be same for mainline and -rt. On -rt, write_trylock_irqsave() doesn't disable irqs and hence the problem is avoided. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED

Re: [PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-10 Thread Sripathi Kodi
Hi Andrew, On Thursday 10 May 2007 07:20, you wrote: On Wed, 9 May 2007 14:13:27 +0530 Sripathi Kodi [EMAIL PROTECTED] wrote: snip old patch Your changelogs aren't vey logical. The context for this change is off in a different patch. I reproduce it here: I am trying to fix the BUG I

Re: [PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-09 Thread Sripathi Kodi
On Thursday 10 May 2007 07:20, Andrew Morton wrote: > On Wed, 9 May 2007 14:13:27 +0530 Sripathi Kodi <[EMAIL PROTECTED]> wrote: > > Hi, > > > > This patch makes ptrace_attach use write_trylock_irqsave. > > > > Signed-off-by: Sripathi Kodi <[EMAIL PR

[PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-09 Thread Sripathi Kodi
Hi, This patch makes ptrace_attach use write_trylock_irqsave. Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> --- kernel/ptrace.c |7 +++ 1 files changed, 3 insertions(+), 4 deletions(-) Index: linux-2.6.21/kernel/pt

[PATCH 1/2] Introduce write_trylock_irqsave

2007-05-09 Thread Sripathi Kodi
and write_trylock. I wish to add write_trylock_irqsave to mainline kernel and then fix the -rt specific problem using this. The patch below adds write_trylock_irqsave function. Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> --- include/linux/spinlock.h |2 ++ include

[PATCH 1/2] Introduce write_trylock_irqsave

2007-05-09 Thread Sripathi Kodi
and write_trylock. I wish to add write_trylock_irqsave to mainline kernel and then fix the -rt specific problem using this. The patch below adds write_trylock_irqsave function. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] --- include/linux/spinlock.h |2 ++ include/linux/spinlock_api_smp.h

[PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-09 Thread Sripathi Kodi
Hi, This patch makes ptrace_attach use write_trylock_irqsave. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] --- kernel/ptrace.c |7 +++ 1 files changed, 3 insertions(+), 4 deletions(-) Index: linux-2.6.21/kernel/ptrace.c

Re: [PATCH 2/2] Use write_trylock_irqsave in ptrace_attach

2007-05-09 Thread Sripathi Kodi
On Thursday 10 May 2007 07:20, Andrew Morton wrote: On Wed, 9 May 2007 14:13:27 +0530 Sripathi Kodi [EMAIL PROTECTED] wrote: Hi, This patch makes ptrace_attach use write_trylock_irqsave. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] --- kernel/ptrace.c |7 +++ 1 files

[PREEMPT_RT] [PATCH] scheduling with irqs disabled: strace/0x00000000/2011

2007-04-20 Thread Sripathi Kodi
think we should do write_unlock_irq(tasklist_lock) before sending SIGSTOP. The following patch solves the problem for me. Thanks and regards, Sripathi. Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> --- linux-2.6.21-rc6-rt0-org/kernel/ptrace.c2007-04-06 08:06:56.0 +05

[PREEMPT_RT] [PATCH] scheduling with irqs disabled: strace/0x00000000/2011

2007-04-20 Thread Sripathi Kodi
and regards, Sripathi. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] --- linux-2.6.21-rc6-rt0-org/kernel/ptrace.c2007-04-06 08:06:56.0 +0530 +++ linux-2.6.21-rc6-rt0/kernel/ptrace.c2007-04-19 18:18:40.0 +0530 @@ -205,10 +205,16 @@ repeat: __ptrace_link

x86_64: How to disable local APIC timer interrupts?

2005-04-18 Thread Sripathi Kodi
Hi, I am trying to disable the local APIC timer interrupts on x86_64 machine, but finding that it just doesn't work. I am trying to find out if I am doing something wrong or if there is a problem with these CPUs. I have a dual-cpu x86_64 machine and I have booted up with 2.6.11 kernel and

x86_64: How to disable local APIC timer interrupts?

2005-04-18 Thread Sripathi Kodi
Hi, I am trying to disable the local APIC timer interrupts on x86_64 machine, but finding that it just doesn't work. I am trying to find out if I am doing something wrong or if there is a problem with these CPUs. I have a dual-cpu x86_64 machine and I have booted up with 2.6.11 kernel and

[PATCH] s390: getdents patch for 32 -> 64 converter

2005-02-01 Thread Sripathi Kodi
(http://ozlabs.org/pipermail/linuxppc64-dev/2004-March/001359.html) and was integrated into 2.6.5. Thanks, Sripathi. Signed-off-by: Sripathi Kodi <[EMAIL PROTECTED]> --- linux-2.6.10/arch/s390/kernel/compat_linux.c2004-12-25 03:05:24.0 +0530 +++ /home/sripathi/12795/ma

[PATCH] s390: getdents patch for 32 - 64 converter

2005-02-01 Thread Sripathi Kodi
(http://ozlabs.org/pipermail/linuxppc64-dev/2004-March/001359.html) and was integrated into 2.6.5. Thanks, Sripathi. Signed-off-by: Sripathi Kodi [EMAIL PROTECTED] --- linux-2.6.10/arch/s390/kernel/compat_linux.c2004-12-25 03:05:24.0 +0530 +++ /home/sripathi/12795/mainline