Hi,
On Wed, Jan 16, 2008 at 04:33:12PM +0900, KOSAKI Motohiro wrote:
> Hi Clifford,
>
> > +static inline char *task_rlim(struct task_struct *p, char *buffer)
> > +{
> > + unsigned long flags;
> > + struct rlimit rlim[RLIM_NLIMITS];
> > + int i;
> > +
> > + rcu_read_lock();
> > + if
Hi,
On Wed, Jan 16, 2008 at 04:33:12PM +0900, KOSAKI Motohiro wrote:
Hi Clifford,
+static inline char *task_rlim(struct task_struct *p, char *buffer)
+{
+ unsigned long flags;
+ struct rlimit rlim[RLIM_NLIMITS];
+ int i;
+
+ rcu_read_lock();
+ if
_task_sighand()?
oh fsck! thanks for that pointer..
Here is a new version of the patch which solves this issue and the issues
adressed earlier in this thread by kosaki.
yours,
- clifford
Signed-off-by: Clifford Wolf <[EMAIL PROTECTED]>
--- linux/fs/proc/array.c (revision 750)
+++ li
Hi,
On Tue, Jan 15, 2008 at 07:47:22PM +0900, KOSAKI Motohiro wrote:
> sound good for me.
> a few question please.
>
> > + for (i=0; i > + if (rlim_names[i])
> > + buffer += sprintf(buffer, "Rlim%s:\t", rlim_names[i]);
> > + else
> > +
and 'injecting' a getrlimit() call does not count.. ;-).
yours,
- clifford
Signed-off-by: Clifford Wolf <[EMAIL PROTECTED]>
--- linux/fs/proc/array.c (revision 757)
+++ linux/fs/proc/array.c (working copy)
@@ -239,6 +239,55 @@
}
}
+static char *rlim_names[RLIM_N
and 'injecting' a getrlimit() call does not count.. ;-).
yours,
- clifford
Signed-off-by: Clifford Wolf [EMAIL PROTECTED]
--- linux/fs/proc/array.c (revision 757)
+++ linux/fs/proc/array.c (working copy)
@@ -239,6 +239,55 @@
}
}
+static char *rlim_names[RLIM_NLIMITS
Hi,
On Tue, Jan 15, 2008 at 07:47:22PM +0900, KOSAKI Motohiro wrote:
sound good for me.
a few question please.
+ for (i=0; iRLIM_NLIMITS; i++) {
+ if (rlim_names[i])
+ buffer += sprintf(buffer, Rlim%s:\t, rlim_names[i]);
+ else
+
! thanks for that pointer..
Here is a new version of the patch which solves this issue and the issues
adressed earlier in this thread by kosaki.
yours,
- clifford
Signed-off-by: Clifford Wolf [EMAIL PROTECTED]
--- linux/fs/proc/array.c (revision 750)
+++ linux/fs/proc/array.c (revision
Hi,
In current 2.6.23 (I have checked 2.6.23.12 and 2.6.23.9) the end of
include/asm-powerpc/systbl.h reads:
--snip--
SYSCALL_SPU(getcpu)
COMPAT_SYS(epoll_pwait)
COMPAT_SYS_SPU(utimensat)
COMPAT_SYS(fallocate)
COMPAT_SYS_SPU(signalfd)
COMPAT_SYS_SPU(timerfd)
SYSCALL_SPU(eventfd)
Hi,
In current 2.6.23 (I have checked 2.6.23.12 and 2.6.23.9) the end of
include/asm-powerpc/systbl.h reads:
--snip--
SYSCALL_SPU(getcpu)
COMPAT_SYS(epoll_pwait)
COMPAT_SYS_SPU(utimensat)
COMPAT_SYS(fallocate)
COMPAT_SYS_SPU(signalfd)
COMPAT_SYS_SPU(timerfd)
SYSCALL_SPU(eventfd)
Hi Shannon, hi lkml,
I'm writing a driver for the built-in DMA controller of the Freescale
MPC8349E PowerPC based microcontroller. Unfortunately the DMA-Engine
API seams to be the totally wrong thing for that since this DMA controller
has many features which are not available thru dmaengine
Hi Shannon, hi lkml,
I'm writing a driver for the built-in DMA controller of the Freescale
MPC8349E PowerPC based microcontroller. Unfortunately the DMA-Engine
API seams to be the totally wrong thing for that since this DMA controller
has many features which are not available thru dmaengine
Hi,
I'm curently working on an embedded project using the Freescale MPC8349E
microcontroller (PPC e300 core + almost everything one needs for
communicating with the rest of the world on one ~100$ chip).
One feature of that microcontroller is a generic memory-2-memory four
channel dma controller.
Hi,
I'm curently working on an embedded project using the Freescale MPC8349E
microcontroller (PPC e300 core + almost everything one needs for
communicating with the rest of the world on one ~100$ chip).
One feature of that microcontroller is a generic memory-2-memory four
channel dma controller.
Hey,
On Fri, Jun 15, 2007 at 11:16:08AM +0200, Jan Engelhardt wrote:
> >> so which one is preferred for the kernel?
>
> err = very_long_function_name(lots_of_arguments,
> less,
> less,
> less,
>
Hey,
On Fri, Jun 15, 2007 at 11:16:08AM +0200, Jan Engelhardt wrote:
so which one is preferred for the kernel?
err = very_long_function_name(lots_of_arguments,
less,
less,
less,
Hi kumar (spi_mpc83xx maintainer), Hi list,
the MPC83xx SPI controller clock divider can divide the system clock by not
more then 1024. The spi_mpc83xx driver does not check this and silently
writes garbage to the SPI controller registers when asked to run at lower
frequencies. I've tried to run
Hi kumar (spi_mpc83xx maintainer), Hi list,
the MPC83xx SPI controller clock divider can divide the system clock by not
more then 1024. The spi_mpc83xx driver does not check this and silently
writes garbage to the SPI controller registers when asked to run at lower
frequencies. I've tried to run
Hi,
afaics there is no mechanism in the official kernel tree to handle
interrupts in user space yet. I'd need that for an embedded project I'm
woking on atm and are so far not sure if I'm going to implement such a
generic interface or just write a simple driver that does the job for my
Hi,
afaics there is no mechanism in the official kernel tree to handle
interrupts in user space yet. I'd need that for an embedded project I'm
woking on atm and are so far not sure if I'm going to implement such a
generic interface or just write a simple driver that does the job for my
ux Sources are available for download on the ROCK Linux
Homepage. The package sources used by ROCK Linux will show up on the ROCK
Linux mirrors withing the next couple of days.
A lot of fun and happy hacking,
- Clifford Wolf (Proj
ux Sources are available for download on the ROCK Linux
Homepage. The package sources used by ROCK Linux will show up on the ROCK
Linux mirrors withing the next couple of days.
A lot of fun and happy hacking,
- Clifford Wolf (Proj
22 matches
Mail list logo
