hi,
El Mon, Apr 23, 2007 at 09:40:19AM +0200 Eddie C. Dost ha dit:
> as long as mutexes are not converted to nop when CONFIG_SMP is not
> defined (I don't know what current kernels do), this is of course
> correct. You need to verify the headerfiles for the above.
i just checked this, neither
On Sun, 22 Apr 2007, Parag Warudkar wrote:
> @@ -1097,8 +1097,13 @@
>
> /* Driver specific per-device data */
> chip = kzalloc(sizeof(*chip), GFP_KERNEL);
> - if (chip == NULL)
> + devname = kmalloc(DEVNAME_SIZE, GFP_KERNEL);
> + + if (chip == NULL || devname == NULL) {
Hi,
Please note that the semaphore is used to lock the idt77252 config
tables among multiple users including atmsigd even on single processor
machines. Does this work with mutexes?
Best regards,
Eddie
On Mon, Apr 23, 2007 at 08:55:20AM +0200, Matthias Kaehlcke wrote:
> El Sun, Apr 22, 2007 at
Hi,
as long as mutexes are not converted to nop when CONFIG_SMP is not
defined (I don't know what current kernels do), this is of course
correct. You need to verify the headerfiles for the above.
Regards,
Eddie
On Mon, Apr 23, 2007 at 09:40:26AM +0200, Matthias Kaehlcke wrote:
> El Mon, Apr 23,
El Mon, Apr 23, 2007 at 09:16:08AM +0200 Eddie C. Dost ha dit:
> Please note that the semaphore is used to lock the idt77252 config
> tables among multiple users including atmsigd even on single processor
> machines. Does this work with mutexes?
afaik mutexes have the same behaviour as binary
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> > do need reinforcement and test results on the basic part: _can_ this
> > design be interactive enough on the desktop? So far the feedback has
> > been affirmative, but more testing is needed.
>
> It seems to be fairly easy to make a scheduler
On Sun, Apr 22 2007, Brad Campbell wrote:
> Jens Axboe wrote:
> >
> >Thanks for testing Brad, be sure to use the next patch I sent instead.
> >The one from this mail shouldn't even get you booted. So double check
> >that you are still using CFQ :-)
> >
>
> [184901.576773] BUG: unable to handle
> For a typical, non-linux-geek user there are just two states of the device -
> available and not available. Ububtu is famous for its end-user support.
> They ship your driver since linux-2.6.17. But they pack it in one module.
> And that is _much_ easier, then a hotplug script.
No, we ship a
On Mon, Apr 23, 2007 at 09:10:50AM +0200, Ingo Molnar wrote:
>
> * Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > > yeah - but they'll all be quad core, so the SMP timeslice
> > > multiplicator should do the trick. Most of the CFS testers use
> > > single-CPU systems.
> >
> > But desktop users
Hi,
The tool estimates the cross-chunk references from an extt2/3 file
system. It considers a block group as one chunk and calcuates how many
block groups does a file span across. So, the block group size gives
the estimate of chunk size.
The file systems were aged for about 3-4 months on a
use mutex instead of binary semaphore in idt77252 driver
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/atm/idt77252.c b/drivers/atm/idt77252.c
index b4b8014..e3cf141 100644
--- a/drivers/atm/idt77252.c
+++ b/drivers/atm/idt77252.c
@@ -2430,7 +2430,7 @@
use mutex instead of binary semaphore in CDU-31A driver
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/cdrom/cdu31a.c b/drivers/cdrom/cdu31a.c
index 2157c58..d3649e4 100644
--- a/drivers/cdrom/cdu31a.c
+++ b/drivers/cdrom/cdu31a.c
@@ -263,7 +263,7 @@ static int
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> > yeah - but they'll all be quad core, so the SMP timeslice
> > multiplicator should do the trick. Most of the CFS testers use
> > single-CPU systems.
>
> But desktop users could have have quad thread and even 8 thread CPUs
> soon, so if the number
On Sun, 22 Apr 2007 23:49:41 +0200
Arnd Bergmann wrote:
> On Sunday 22 April 2007, Vitaly Bordug wrote:
> > This utilizes PCMCIA on mpc885ads and mpc866ads from arch/powerpc.
> > In the new approach, direct IMMR accesses from within drivers/ were
> > totally eliminated, that requires
On Sun, Apr 22, 2007 at 03:15:22PM +0300, Sergey Yanovich wrote:
> For a typical, non-linux-geek user there are just two states of the device -
> available and not available. Ububtu is famous for its end-user support.
> They ship your driver since linux-2.6.17. But they pack it in one module.
>
On Sun, 22 Apr 2007 10:40:51 -0700,
Greg KH <[EMAIL PROTECTED]> wrote:
> > Looking some more, kobject_get_path() is used for kobject renaming,
> > uevent handling, and a little bit in the input core. None of these things
> > should try to access a kobject after it has been del()ed. After all,
On Monday 23 April 2007 00:35, Con Kolivas wrote:
> On Monday 23 April 2007 00:22, Willy Tarreau wrote:
> > X is still somewhat jerky, even
> > at nice -19. I'm sure it happens when it's waiting in the other array. We
> > should definitely manage to get rid of this if we want to ensure low
> >
John,
On Fri, 2007-04-20 at 15:15 +0200, John Sigler wrote:
> I've tweaked patch-2.6.20-rt8(*) so that it applies to 2.6.20.7
> (*) http://rt.wiki.kernel.org/index.php/Main_Page
>
> The original patch can be found here:
> http://people.redhat.com/mingo/realtime-preempt/older/patch-2.6.20-rt8
>
On Mon, Apr 23, 2007 at 03:40:21PM +0900, Tejun Heo wrote:
> Hello, Dmitry.
>
> Dmitry Torokhov wrote:
> > Isn't think a good thing? By decoupling the 2 layers we insulate them
> > from changes in each other. This allows bug subsystems to concentrate
> > on topics that important to them instead
El Sun, Apr 22, 2007 at 07:50:36PM -0400 Kyle Moffett ha dit:
> On Apr 22, 2007, at 17:39:59, Matthias Kaehlcke wrote:
> >use spinlock instead of binary mutex in idt77252 driver
>
> I think you really meant: "Use mutex instead of binary semaphore in
> idt77252 driver", since this is a binary
On Mon, 23 Apr 2007, Neil Brown wrote:
> Another option might be to name each cache actually created with a
> unique name, and then create a symlink for each cache that was asked
> for (whether it was created or whether a pre-existing cache was used).
> Then being lazy about deletion shouldn't be
On Thursday April 19, [EMAIL PROTECTED] wrote:
>
> Right. Sigh. But there is no user of the symlinks.
>
> I could drop the symlinks completely. Just do not track what names a cache
> aliases to?
>
Suppose I have a kmem_cache which at different times has different
sizes (like, for example, the
On Mon, 23 Apr 2007, Rik van Riel wrote:
William Heimbigner wrote:
If there was 1) a maintainer and 2) code that didn't break "coding
standards", would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills
these criteria (and is useful to have -
On Mon, 23 Apr 2007 08:29:59 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > > What about swapout? That can increase the number of writeback pages,
> > > without decreasing the number of dirty pages, no?
> >
> > Could we not solve that by enabling cap_account_writeback on
> > swapper_space,
Hello, Dmitry.
Dmitry Torokhov wrote:
> Isn't think a good thing? By decoupling the 2 layers we insulate them
> from changes in each other. This allows bug subsystems to concentrate
> on topics that important to them instead of worying about refcounting
> objects that are not directly interesting
> > > > The other deadlock, in throttle_vm_writeout() is still to be solved.
> > >
> > > Let's go back to the original changelog:
> > >
> > > Author: marcelo.tosatti
> > > Date: Tue Mar 8 17:25:19 2005 +
> > >
> > > [PATCH] vm: pageout throttling
> > >
> > > With silly
On Mon, Apr 23, 2007 at 12:17:22AM -0600, Eric W. Biederman wrote:
> Vivek Goyal <[EMAIL PROTECTED]> writes:
>
> > On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
> >> +++ b/arch/x86_64/Kconfig
> >> @@ -565,62 +565,9 @@ config CRASH_DUMP
> >>which are loaded in the
William Heimbigner wrote:
If there was 1) a maintainer and 2) code that didn't break "coding
standards", would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills
these criteria (and is useful to have - reiser4 seems to have
enough user interest)
* Markus Trippelsdorf <[EMAIL PROTECTED]> wrote:
> > The new version does not link here (amd64,smp):
> >
> > LD .tmp_vmlinux1
> > arch/x86_64/kernel/built-in.o:(.rodata+0x1dd8): undefined reference to
> > `sys_yield_to'
>
> Changing sys_yield_to to sys_sched_yield_to in
>
Vivek Goyal <[EMAIL PROTECTED]> writes:
> On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
>> +++ b/arch/x86_64/Kconfig
>> @@ -565,62 +565,9 @@ config CRASH_DUMP
>>which are loaded in the main kernel with kexec-tools into
>>a specially reserved region and
On Sun, 22 Apr 2007, Andrew Morton wrote:
> This patch causes a use-uninitialised crash in the locks code.
Sigh. The only case in which the check is inverted in a constructor.
Invert the check.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
Index: linux-2.6.21-rc6/fs/locks.c
Hi Ogawa :)
* OGAWA Hirofumi <[EMAIL PROTECTED]> dixit:
> DervishD <[EMAIL PROTECTED]> writes:
> >> It would add the limitation to following simple usage,
> >>
> >># mount -t vfat /dev/sda1 /mnt
> >> # cp -a * /mnt
> >> # umount
> >>
> >> if /dev/sda1 was the large and
Updated patch according to Sam's comments.
/Mikael
diff -urNP --exclude='*.cvsignore'
../linux/arch/cris/arch-v32/boot/compressed/decompress.ld
linux-2.6/arch/cris/arch-v32/boot/compressed/decompress.ld
--- ../linux/arch/cris/arch-v32/boot/compressed/decompress.ld 2007-02-04
19:44:54.0
On Sat, 2007-04-21 at 22:25 +0200, Miklos Szeredi wrote:
> > > The other deadlock, in throttle_vm_writeout() is still to be solved.
> >
> > Let's go back to the original changelog:
> >
> > Author: marcelo.tosatti
> > Date: Tue Mar 8 17:25:19 2005 +
> >
> > [PATCH] vm: pageout
On 4/23/07, William Heimbigner <[EMAIL PROTECTED]> wrote:
Obviously there's a significant number of people interested in reiser4
Count me in.
Jeff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, 23 Apr 2007, Rik van Riel wrote:
William Heimbigner wrote:
However, is the code really in such a shape that the community doesn't
want to maintain it? Obviously there's a significant number of people
interested in reiser4 - if there weren't, questions like this wouldn't
keep
Andrew Morton wrote:
> On Mon, 16 Apr 2007 11:41:14 +0400
> Pavel Emelianov <[EMAIL PROTECTED]> wrote:
>
>> If the thread failed to create the subsequent wait_event
>> will hang forever.
>>
>> This is likely to happen if kernel hits max_threads limit.
>>
>> Will be critical for virtualization
On Fri, 20 Apr 2007 18:39:43 -0700 (PDT) Christoph Lameter <[EMAIL PROTECTED]>
wrote:
> I have never seen a use of SLAB_DEBUG_INITIAL. It is only supported by SLAB.
>
> I think its purpose was to have a callback after an object has been freed
> to verify that the state is the constructor state
William Heimbigner wrote:
However, is the code really in such a shape that the
community doesn't want to maintain it? Obviously there's a significant
number of people interested in reiser4 - if there weren't, questions
like this wouldn't keep getting asked.
There are people interested in
On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
>
> Now that the vmlinux is marked as relocatable there is no reason to
> retain the CONFIG_PHYSICAL_START option, as we can put the binary we
> have at any 2MB aligned address in memory.
>
> With CONFIG_PHYSICAL_START gone the
When data symbols are not present in kernel image, user needs to add
dot(".") before function name explicitly, that he wants to probe in kprobe
module on ppc64.
for ex:-
When data symbols are missing on ppc64,
[EMAIL PROTECTED] ~]# cat /proc/kallsyms | grep do_fork
When data symbols are not present in kernel image, user needs to add
dot(.) before function name explicitly, that he wants to probe in kprobe
module on ppc64.
for ex:-
When data symbols are missing on ppc64,
[EMAIL PROTECTED] ~]# cat /proc/kallsyms | grep do_fork
On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
Now that the vmlinux is marked as relocatable there is no reason to
retain the CONFIG_PHYSICAL_START option, as we can put the binary we
have at any 2MB aligned address in memory.
With CONFIG_PHYSICAL_START gone the handful
William Heimbigner wrote:
However, is the code really in such a shape that the
community doesn't want to maintain it? Obviously there's a significant
number of people interested in reiser4 - if there weren't, questions
like this wouldn't keep getting asked.
There are people interested in
On Fri, 20 Apr 2007 18:39:43 -0700 (PDT) Christoph Lameter [EMAIL PROTECTED]
wrote:
I have never seen a use of SLAB_DEBUG_INITIAL. It is only supported by SLAB.
I think its purpose was to have a callback after an object has been freed
to verify that the state is the constructor state again?
Andrew Morton wrote:
On Mon, 16 Apr 2007 11:41:14 +0400
Pavel Emelianov [EMAIL PROTECTED] wrote:
If the thread failed to create the subsequent wait_event
will hang forever.
This is likely to happen if kernel hits max_threads limit.
Will be critical for virtualization systems that limit
On Mon, 23 Apr 2007, Rik van Riel wrote:
William Heimbigner wrote:
However, is the code really in such a shape that the community doesn't
want to maintain it? Obviously there's a significant number of people
interested in reiser4 - if there weren't, questions like this wouldn't
keep
On 4/23/07, William Heimbigner [EMAIL PROTECTED] wrote:
Obviously there's a significant number of people interested in reiser4
Count me in.
Jeff.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Sat, 2007-04-21 at 22:25 +0200, Miklos Szeredi wrote:
The other deadlock, in throttle_vm_writeout() is still to be solved.
Let's go back to the original changelog:
Author: marcelo.tosatti marcelo.tosatti
Date: Tue Mar 8 17:25:19 2005 +
[PATCH] vm: pageout
Updated patch according to Sam's comments.
/Mikael
diff -urNP --exclude='*.cvsignore'
../linux/arch/cris/arch-v32/boot/compressed/decompress.ld
linux-2.6/arch/cris/arch-v32/boot/compressed/decompress.ld
--- ../linux/arch/cris/arch-v32/boot/compressed/decompress.ld 2007-02-04
19:44:54.0
Hi Ogawa :)
* OGAWA Hirofumi [EMAIL PROTECTED] dixit:
DervishD [EMAIL PROTECTED] writes:
It would add the limitation to following simple usage,
# mount -t vfat /dev/sda1 /mnt
# cp -a * /mnt
# umount
if /dev/sda1 was the large and slow device, mount will
Vivek Goyal [EMAIL PROTECTED] writes:
On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
+++ b/arch/x86_64/Kconfig
@@ -565,62 +565,9 @@ config CRASH_DUMP
which are loaded in the main kernel with kexec-tools into
a specially reserved region and then later
On Sun, 22 Apr 2007, Andrew Morton wrote:
This patch causes a use-uninitialised crash in the locks code.
Sigh. The only case in which the check is inverted in a constructor.
Invert the check.
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
Index: linux-2.6.21-rc6/fs/locks.c
William Heimbigner wrote:
If there was 1) a maintainer and 2) code that didn't break coding
standards, would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills
these criteria (and is useful to have - reiser4 seems to have
enough user interest) usually
* Markus Trippelsdorf [EMAIL PROTECTED] wrote:
The new version does not link here (amd64,smp):
LD .tmp_vmlinux1
arch/x86_64/kernel/built-in.o:(.rodata+0x1dd8): undefined reference to
`sys_yield_to'
Changing sys_yield_to to sys_sched_yield_to in
On Mon, Apr 23, 2007 at 12:17:22AM -0600, Eric W. Biederman wrote:
Vivek Goyal [EMAIL PROTECTED] writes:
On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
+++ b/arch/x86_64/Kconfig
@@ -565,62 +565,9 @@ config CRASH_DUMP
which are loaded in the main kernel
The other deadlock, in throttle_vm_writeout() is still to be solved.
Let's go back to the original changelog:
Author: marcelo.tosatti marcelo.tosatti
Date: Tue Mar 8 17:25:19 2005 +
[PATCH] vm: pageout throttling
With silly pageout testcases it
On Mon, 23 Apr 2007 08:29:59 +0200 Miklos Szeredi [EMAIL PROTECTED] wrote:
What about swapout? That can increase the number of writeback pages,
without decreasing the number of dirty pages, no?
Could we not solve that by enabling cap_account_writeback on
swapper_space, and thereby
Hello, Dmitry.
Dmitry Torokhov wrote:
Isn't think a good thing? By decoupling the 2 layers we insulate them
from changes in each other. This allows bug subsystems to concentrate
on topics that important to them instead of worying about refcounting
objects that are not directly interesting for
On Mon, 23 Apr 2007, Rik van Riel wrote:
William Heimbigner wrote:
If there was 1) a maintainer and 2) code that didn't break coding
standards, would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills
these criteria (and is useful to have - reiser4
On Thursday April 19, [EMAIL PROTECTED] wrote:
Right. Sigh. But there is no user of the symlinks.
I could drop the symlinks completely. Just do not track what names a cache
aliases to?
Suppose I have a kmem_cache which at different times has different
sizes (like, for example, the cache
On Mon, 23 Apr 2007, Neil Brown wrote:
Another option might be to name each cache actually created with a
unique name, and then create a symlink for each cache that was asked
for (whether it was created or whether a pre-existing cache was used).
Then being lazy about deletion shouldn't be a
El Sun, Apr 22, 2007 at 07:50:36PM -0400 Kyle Moffett ha dit:
On Apr 22, 2007, at 17:39:59, Matthias Kaehlcke wrote:
use spinlock instead of binary mutex in idt77252 driver
I think you really meant: Use mutex instead of binary semaphore in
idt77252 driver, since this is a binary semaphore
On Mon, Apr 23, 2007 at 03:40:21PM +0900, Tejun Heo wrote:
Hello, Dmitry.
Dmitry Torokhov wrote:
Isn't think a good thing? By decoupling the 2 layers we insulate them
from changes in each other. This allows bug subsystems to concentrate
on topics that important to them instead of worying
John,
On Fri, 2007-04-20 at 15:15 +0200, John Sigler wrote:
I've tweaked patch-2.6.20-rt8(*) so that it applies to 2.6.20.7
(*) http://rt.wiki.kernel.org/index.php/Main_Page
The original patch can be found here:
http://people.redhat.com/mingo/realtime-preempt/older/patch-2.6.20-rt8
On Monday 23 April 2007 00:35, Con Kolivas wrote:
On Monday 23 April 2007 00:22, Willy Tarreau wrote:
X is still somewhat jerky, even
at nice -19. I'm sure it happens when it's waiting in the other array. We
should definitely manage to get rid of this if we want to ensure low
latency.
On Sun, Apr 22, 2007 at 03:15:22PM +0300, Sergey Yanovich wrote:
For a typical, non-linux-geek user there are just two states of the device -
available and not available. Ububtu is famous for its end-user support.
They ship your driver since linux-2.6.17. But they pack it in one module.
And
On Sun, 22 Apr 2007 10:40:51 -0700,
Greg KH [EMAIL PROTECTED] wrote:
Looking some more, kobject_get_path() is used for kobject renaming,
uevent handling, and a little bit in the input core. None of these things
should try to access a kobject after it has been del()ed. After all, it's
use mutex instead of binary semaphore in CDU-31A driver
Signed-off-by: Matthias Kaehlcke [EMAIL PROTECTED]
--
diff --git a/drivers/cdrom/cdu31a.c b/drivers/cdrom/cdu31a.c
index 2157c58..d3649e4 100644
--- a/drivers/cdrom/cdu31a.c
+++ b/drivers/cdrom/cdu31a.c
@@ -263,7 +263,7 @@ static int
* Nick Piggin [EMAIL PROTECTED] wrote:
yeah - but they'll all be quad core, so the SMP timeslice
multiplicator should do the trick. Most of the CFS testers use
single-CPU systems.
But desktop users could have have quad thread and even 8 thread CPUs
soon, so if the number doesn't
On Sun, 22 Apr 2007 23:49:41 +0200
Arnd Bergmann wrote:
On Sunday 22 April 2007, Vitaly Bordug wrote:
This utilizes PCMCIA on mpc885ads and mpc866ads from arch/powerpc.
In the new approach, direct IMMR accesses from within drivers/ were
totally eliminated, that requires hardware_enable,
use mutex instead of binary semaphore in idt77252 driver
Signed-off-by: Matthias Kaehlcke [EMAIL PROTECTED]
--
diff --git a/drivers/atm/idt77252.c b/drivers/atm/idt77252.c
index b4b8014..e3cf141 100644
--- a/drivers/atm/idt77252.c
+++ b/drivers/atm/idt77252.c
@@ -2430,7 +2430,7 @@
Hi,
The tool estimates the cross-chunk references from an extt2/3 file
system. It considers a block group as one chunk and calcuates how many
block groups does a file span across. So, the block group size gives
the estimate of chunk size.
The file systems were aged for about 3-4 months on a
On Mon, Apr 23, 2007 at 09:10:50AM +0200, Ingo Molnar wrote:
* Nick Piggin [EMAIL PROTECTED] wrote:
yeah - but they'll all be quad core, so the SMP timeslice
multiplicator should do the trick. Most of the CFS testers use
single-CPU systems.
But desktop users could have have
For a typical, non-linux-geek user there are just two states of the device -
available and not available. Ububtu is famous for its end-user support.
They ship your driver since linux-2.6.17. But they pack it in one module.
And that is _much_ easier, then a hotplug script.
No, we ship a udev
* Nick Piggin [EMAIL PROTECTED] wrote:
do need reinforcement and test results on the basic part: _can_ this
design be interactive enough on the desktop? So far the feedback has
been affirmative, but more testing is needed.
It seems to be fairly easy to make a scheduler interactive if
El Mon, Apr 23, 2007 at 09:16:08AM +0200 Eddie C. Dost ha dit:
Please note that the semaphore is used to lock the idt77252 config
tables among multiple users including atmsigd even on single processor
machines. Does this work with mutexes?
afaik mutexes have the same behaviour as binary
On Sun, Apr 22 2007, Brad Campbell wrote:
Jens Axboe wrote:
Thanks for testing Brad, be sure to use the next patch I sent instead.
The one from this mail shouldn't even get you booted. So double check
that you are still using CFQ :-)
[184901.576773] BUG: unable to handle kernel NULL
Hi,
Please note that the semaphore is used to lock the idt77252 config
tables among multiple users including atmsigd even on single processor
machines. Does this work with mutexes?
Best regards,
Eddie
On Mon, Apr 23, 2007 at 08:55:20AM +0200, Matthias Kaehlcke wrote:
El Sun, Apr 22, 2007 at
Hi,
as long as mutexes are not converted to nop when CONFIG_SMP is not
defined (I don't know what current kernels do), this is of course
correct. You need to verify the headerfiles for the above.
Regards,
Eddie
On Mon, Apr 23, 2007 at 09:40:26AM +0200, Matthias Kaehlcke wrote:
El Mon, Apr 23,
On Sun, 22 Apr 2007, Parag Warudkar wrote:
@@ -1097,8 +1097,13 @@
/* Driver specific per-device data */
chip = kzalloc(sizeof(*chip), GFP_KERNEL);
- if (chip == NULL)
+ devname = kmalloc(DEVNAME_SIZE, GFP_KERNEL);
+ + if (chip == NULL || devname == NULL) {
Hi,
this
hi,
El Mon, Apr 23, 2007 at 09:40:19AM +0200 Eddie C. Dost ha dit:
as long as mutexes are not converted to nop when CONFIG_SMP is not
defined (I don't know what current kernels do), this is of course
correct. You need to verify the headerfiles for the above.
i just checked this, neither the
On Mon, Apr 23, 2007 at 10:14:27AM +0400, Vitaly Bordug wrote:
On Sun, 22 Apr 2007 23:49:41 +0200
Arnd Bergmann wrote:
On Sunday 22 April 2007, Vitaly Bordug wrote:
This utilizes PCMCIA on mpc885ads and mpc866ads from arch/powerpc.
In the new approach, direct IMMR accesses from within
On Sun, 22 Apr 2007 23:13:54 + (GMT) William Heimbigner [EMAIL PROTECTED]
wrote:
On running pktsetup 0 /dev/hdd, I get the following:
[ 3970.461403] =
[ 3970.482051] [ INFO: possible recursive locking detected ]
[ 3970.498210] 2.6.21-rc7 #2
Hi,
On 4/23/07, Eddie C. Dost [EMAIL PROTECTED] wrote:
as long as mutexes are not converted to nop when CONFIG_SMP is not
defined (I don't know what current kernels do), this is of course
correct. You need to verify the headerfiles for the above.
Yes, even on UP different threads accessing
Thomas Gleixner wrote:
On Fri, 2007-04-20 at 15:15 +0200, John Sigler wrote:
I've tweaked patch-2.6.20-rt8(*) so that it applies to 2.6.20.7
(*) http://rt.wiki.kernel.org/index.php/Main_Page
The original patch can be found here:
On Mon, 23 Apr 2007 06:42:24 + (GMT) William Heimbigner [EMAIL PROTECTED]
wrote:
On Mon, 23 Apr 2007, Rik van Riel wrote:
William Heimbigner wrote:
If there was 1) a maintainer and 2) code that didn't break coding
standards, would it be included in the kernel?
While I cannot
Andrew Morton wrote:
On Wed, 18 Apr 2007 11:13:01 +0400 Pavel Emelianov [EMAIL PROTECTED] wrote:
The out_of_memory() function and SysRq-M handler call
show_mem() to show the current memory usage state.
This is also helpful to see which slabs are the largest
in the system.
Thanks Pekka for
Considering where it failed and that 2.6.20.3 worked, I would be
extremely surprised if this wasn't one more report of
adjust-legacy-ide-resource-setting.patch breaking booting (and we
already have confirmed reports for this)...
But AFAIK we still don't understand how this patch managed to
Hello Greg,
On Sun, Apr 22, 2007 at 10:47:17PM -0700, Greg KH wrote:
On Fri, Apr 20, 2007 at 10:58:53AM +0200, Wolfgang Erig wrote:
Hello,
I have a regression with 2.6.21-rc7-g80d74d51.
The utility gammu to talk to my mobile does not work anymore.
With 2.6.20 gammu runs fine.
On 4/22/07, Luca Tettamanti [EMAIL PROTECTED] wrote:
Probably the two siblings are enumerated only in ACPI tables. If you
disable ACPI the kernel won't be aware of the second core.
Luca
--
Su cio` di cui non si puo` parlare e` bene tacere.
Ludwig Wittgenstein
On 4/23/07, Robert Hancock
On Mon, 2007-04-23 at 10:03 +0200, John Sigler wrote:
Can you create an entry in the rt-wiki, so people can find your
patches ?
Sure.
Should I add a link to my patch on the CONFIG PREEMPT RT Patch page?
http://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch#Download
e.g. in the
On Sun, Apr 22, 2007 at 07:50:36PM -0400, Kyle Moffett wrote:
On Apr 22, 2007, at 17:39:59, Matthias Kaehlcke wrote:
use spinlock instead of binary mutex in idt77252 driver
I think you really meant: Use mutex instead of binary semaphore in
idt77252 driver, since this is a binary semaphore
El Mon, Apr 23, 2007 at 09:17:53AM +0100 Christoph Hellwig ha dit:
On Sun, Apr 22, 2007 at 07:50:36PM -0400, Kyle Moffett wrote:
On Apr 22, 2007, at 17:39:59, Matthias Kaehlcke wrote:
use spinlock instead of binary mutex in idt77252 driver
I think you really meant: Use mutex instead of
We only care when del_timer() returns true. In that case, if the timer
function still runs (possible for single-threaded wqs), it has already
passed __queue_work().
Why do you assume that?
David
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Hello David,
Thursday, April 19, 2007, 5:22:44 AM, you wrote:
So, talking about what an (optional) implementation framework might
look like (and which could handle the SOC, FPGA, I2C, and MFD cases
I've looked at):
See patches in following messages ... a preliminary gpio_chip core
On Fri, Apr 20, 2007 at 09:08:36PM +0400, Oleg Nesterov wrote:
On 04/20, Jarek Poplawski wrote:
On Thu, Apr 19, 2007 at 02:21:22PM +0400, Oleg Nesterov wrote:
...
Yes. It would be better to use cancel_work_sync() instead of
flush_workqueue()
to make this less possible (because
On Thu, 29 Mar 2007 02:37:38 +1000 Con Kolivas [EMAIL PROTECTED] wrote:
test.kernel.org found some idle time regressions in the latest update to the
staircase deadline scheduler and Andy Whitcroft helped me track down the
offending problem which was present in all previous RSDL schedulers but
Hi all,
this is a very simple module that allows bind() to tcp/udp port (=1024)
only for the uids defined in a configfs tree.
It is a first version, it only works for PF_INET sockets and makes no
difference between tcp and udp (i am working on this)
For (little) more info see
On Mon, 2007-04-23 at 02:16 +0530, Karuna sagar K wrote:
Hi,
For some time I had been working on this file system test framework.
Now I have a implementation for the same and below is the explanation.
Any comments are welcome.
Introduction:
The testing tools and benchmarks available
401 - 500 of 881 matches
Mail list logo
