Re: [PATCH] sched domain debug sysctl fixes

2007-10-15 Thread Ingo Molnar 

* Milton Miller <[EMAIL PROTECTED]> wrote:

> The following 5 patches provide fixes for the sysctl code added under 
> CONFIG_DEBUG_SCHED.  After debugging a boot failure dereferencing not 
> per-cpu data for an impossible cpu, I found the other issues by 
> inspection.
> 
> Following these fixes, /proc/sysctl/kernel/sched_debug/ should work 
> with exclusive cpusets, cpu hotplug, offline and not present cpus, and 
> will show all 11 files.

thanks, great fixes! They should show up in the next sched-devel git 
tree.

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] sched domain debug sysctl fixes

2007-10-12 Thread Milton Miller 

I forgot to put the seqence numbers in the patch subjects (I did
in the message ids).

Here is the order I diffed them:

sched domain sysctl: register online cpus
sched domain sysctl: free and rebuild when changing domains
sched.c: use kcalloc
sched domain sysctl: don't bug on alloc failure
sched domain sysctl: sysctl tables can have no holes

milton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] sched domain debug sysctl fixes

2007-10-12 Thread Milton Miller 
The following 5 patches provide fixes for the sysctl code added under
CONFIG_DEBUG_SCHED.   After debugging a boot failure dereferencing
not per-cpu data for an impossible cpu, I found the other issues by
inspection.

Following these fixes, /proc/sysctl/kernel/sched_debug/ should work with
exclusive cpusets, cpu hotplug, offline and not present cpus, and will
show all 11 files.

milton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/