On Tue, 10 Apr 2007, Roland Dreier wrote:
> > >but that's where you would use the more explicit
> > >__RAW_SPIN_LOCK_UNLOCKED, no? AFAIK, you really can remove the macro
> > >SPIN_LOCK_UNLOCKED in its entirety.
> >
> > I don't remember LDD speaking about __RAW_*. (And other than not
> > hav
On Sunday April 8, [EMAIL PROTECTED] wrote:
> On Sun, 8 April 2007 11:11:20 -0700, H. Peter Anvin wrote:
> >
> > Well, the question is if you can keep the seekdir/telldir cookie around
> > as a pointer -- preferrably in userspace, of course. You would
> > presumably garbage-collect them on clos
On 4/10/07, Neil Brown <[EMAIL PROTECTED]> wrote:
2/ Some data structure using an ordered search key that is based on
the filename (e.g. a B-tree with a search key that is a hash of the
filename).
In the first case, you just use a fixed opaque cookie for location in
a directory.
In the secon
Jan Kara <[EMAIL PROTECTED]> writes:
> Hello!
>
> In thread http://lkml.org/lkml/2007/3/9/403, we discussed a problem
> with the current heuristic for detecting sequential IO in
> do_generic_mapping_read() - for small files a page is marked as accessed
> only once which can cause a performanc
> > Don't worry about the __RAW_SPIN_LOCK_UNLOCKED stuff, that's
> > obviously not for generic code to use. The right answer (as I said
> > before) is to use DEFINE_SPINLOCK().
>
> that works fine if you're defining a single spinlock, but what do you
> do in cases like this:
>
> arch/spa
On Wed, 2007-04-11 at 07:37 +1000, Neil Brown wrote:
> On Tuesday April 10, [EMAIL PROTECTED] wrote:
> > On Wed, 2007-04-11 at 07:12 +1000, Neil Brown wrote:
> > >
> > > Is there something that makes that interface problematic?
> >
> > File deletions...
>
> How are they a problem ?
>
> There ar
Chris Wright wrote:
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
+void __init vmi_time_init(void)
+{
+ /* Disable PIT: BIOSes start PIT CH0 with 18.2hz peridic. */
+ outb_p(0x3a, PIT_MODE); /* binary, mode 5, LSB/MSB, ch 0 */
That shouldn't be necessary using clockevents.
Jan Engelhardt wrote:
> the following patch series turns some menus into menuconfigs, so they
> can be disabled whilst "walking" thorugh the parent menu (check the
> videos [1], [2] to see what I mean), enabling for disabling lots of
> options _quickly_.
>
> I'll send the patches (as a reply to
Eric Sandeen wrote:
except in the case of a journaling filesystem, where the journal in
theory obviates the need for a fsck. (yes, I know... fsck still has a
place...) But, fsck is largely meaningless until the journal has been
recovered anyway (fs can only be consistent if it includes uncommit
On Tue, Apr 10, 2007 at 05:45:07PM -0400, Robert P. J. Day wrote:
> that works fine if you're defining a single spinlock, but what do you
> do in cases like this:
>
> arch/sparc/lib/atomic32.c: [0 ... (ATOMIC_HASH_SIZE-1)] =
> SPIN_LOCK_UNLOCKED
>
> that is, when you're assigning an array o
include KERN_* constant in printk() calls in mm/slab.c
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
---
diff --git a/mm/slab.c b/mm/slab.c
index 4cbac24..5a6e8c8 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -2151,13 +2151,15 @@ kmem_cache_create (const char *name, size_t size,
size_t align,
Jan Engelhardt wrote:
> the following patch series turns some menus into menuconfigs, so they
> can be disabled whilst "walking" thorugh the parent menu
Great, but instead of making it a simple on/off, make it tri-state that would
default select all child-options appropriately. (see HW_RANDOM)
On Apr 11 2007 00:04, Stefan Richter wrote:
>
>[...] I tried one of the patches
> - with make xconfig: OK
> - with make gconfig: OK
> - with make menuconfig: less so, because:
>When one switches a menuconfig _on_, one might miss that there are
>subsequent options to configure. (Although the av
On Wed, 11 Apr 2007, Stefan Richter wrote:
Jan Engelhardt wrote:
the following patch series turns some menus into menuconfigs, so they
can be disabled whilst "walking" thorugh the parent menu (check the
videos [1], [2] to see what I mean), enabling for disabling lots of
options _quickly_.
I'll
Zachary Amsden wrote:
>/*
> * Avoid unnecessary state transitions, as it confuses
> * Geode / Cyrix based boxen.
> */
>case CLOCK_EVT_MODE_SHUTDOWN:
>if (evt->mode == CLOCK_EVT_MODE_UNUSED)
>break;
>case CLOCK_E
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> Rather than using a single constant PERCPU_ENOUGH_ROOM, compute it as
> the sum of kernel_percpu + PERCPU_MODULE_RESERVE. This is now common
> to all architectures; if an architecture wants to set
> PERCPU_ENOUGH_ROOM to something special, then it
On Tue, 10 Apr 2007 22:08:29 +0800
WANG Cong <[EMAIL PROTECTED]> wrote:
> Since kobject_add, sysfs_create_link and sysfs_create_file are marked as
> '__must_check', we must always check their return values.
>
> Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
> Acked-by: Cornelia Huck <[EMAIL PROTEC
Eric W. Biederman wrote:
> I think I have already done this but in case I haven't.
> Acked-by: "Eric W. Biederman" <[EMAIL PROTECTED]>
>
> I see any problems there.
>
^don't?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
M
On Tuesday 10 April 2007, Jeff Garzik wrote:
> That's why I feel thread creation -- cheap under Linux -- is quite
> appropriate for many of these situations.
Maybe that (thread creation) can be done at open(), socket-creation,
service request, syscall or whatever event triggers a driver/subsyste
On Sun, 2007-04-08 at 14:35 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
Since 2.6.21-rc5-mm1, one of the test.kernel.org machines (elm3b239) has
not been able to boot because it cannot find the SCSI device. You can
view htt
Jan Engelhardt wrote:
> Use menuconfigs instead of menus, so the whole menu can be disabled at
> once instead of going through all options.
If you excuse the nitpicking: The patch description is not very
precise. You don't have to go through all options in the IEEE 1394 menu
if you don't
On Mon, Apr 09, 2007 at 07:40:52PM +0200, Rafael J. Wysocki wrote:
> On Monday, 9 April 2007 18:14, Pallipadi, Venkatesh wrote:
> >
> > >-Original Message-
> > >From: Rafael J. Wysocki [mailto:[EMAIL PROTECTED]
> > >Sent: Monday, April 09, 2007 9:08 AM
> > >To: Andrew Morton
> > >Cc: linu
Hello all,
First I would like to thank Jean for his great work even if could be seen as
"slow". He did the perfect job, allowing only just perfect code to enter the trees.
I haven't seen anything from Rudolf Marek, but he is definitely
qualified if he wants to step up. I'm personally hoping J
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> Let's allow page-alignment in general for per-cpu data (wanted by Xen, and
> Ingo suggested KVM as well).
>
> Because larger alignments can use more room, we increase the max per-cpu
> memory to 64k rather than 32k: it's getting a little tight.
Th
atomic-avr32-remove-cast
This int cast is superfluous since system.h cmpxchg already casts it in
(typeof(*(ptr))).
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/include/asm-avr32/atomic.h
+++ b/include/asm-avr32/atomic.h
@@ -173,7 +173,7 @@ static inline int atomic_sub_if_positive(i
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> Move some random stuff which doesn't need tasklist_lock from
> reparent_to_init()
> to its caller, daemonize(). Strictly speaking, rlim is protected by
> task_lock()
> but we don't need it to copy init_task->rlim.
Acked-by: "Eric W. Biederman" <[EMAIL
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
> Yes, but unfortunately that is a nop:
>
> /*
> * Avoid unnecessary state transitions, as it confuses
> * Geode / Cyrix based boxen.
> */
> case CLOCK_EVT_MODE_SHUTDOWN:
> if (evt->mode == CLOCK
Jeremy Fitzhardinge wrote:
Why not submit a patch to do what you need here? (The Geode comment is
a bit worrying though.)
Why should VMI add workaround into PIT code? PIT code wants to know
nothing about VMI. It understands PIT timers on hardware. VMI, on the
other hand, is special - i
I just queued all of this for 2.6.22.
Is there any chance of getting a fix for the use-after-free that can
be caused by allocating something from userspace, failing to mmap the
buffer and then exiting? To see what happens, look at how
ipath_create_cq sticks a struct ipath_mmap_info into the pendi
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>> I think I have already done this but in case I haven't.
>> Acked-by: "Eric W. Biederman" <[EMAIL PROTECTED]>
>>
>> I see any problems there.
>>
> ^don't?
Yep. I did not see any problems with the patch.
Eric
-
To u
On Apr 11 2007 01:12, Al Boldi wrote:
>Jan Engelhardt wrote:
>> the following patch series turns some menus into menuconfigs, so they
>> can be disabled whilst "walking" thorugh the parent menu
>
>Great, but instead of making it a simple on/off, make it tri-state that would
>default select all ch
I applied this, but I still think there's some more work to do in this
area:
> The port sharing feature mixed kernel virtual addresses as well as
> physical addresses for the offset used to describe the mmap address to map
> the InfiniPath hardware into user space. This had a conflict on power
On Tue, 10 Apr 2007 12:46:11 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 10 Apr 2007, Cornelia Huck wrote:
>
> > Whoops:
> >
> > In file included from include/linux/interrupt.h:15,
> > from include/asm/hardirq.h:18,
> > from include/linux/hardirq
Remove duplicated defines in asm-powerpc/atomic.h. atomic64_inc_not_zero
and atomic64_xchg are defined twice. It also removes an unnecessary cast
to the atomic_cmpxchg result, which is already done by system.h cmpxchg.
It applies on 2.6.21-rc6-mm1.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECT
On Tuesday April 10, [EMAIL PROTECTED] wrote:
> On Wed, 2007-04-11 at 07:37 +1000, Neil Brown wrote:
> > On Tuesday April 10, [EMAIL PROTECTED] wrote:
> > > On Wed, 2007-04-11 at 07:12 +1000, Neil Brown wrote:
> > > >
> > > > Is there something that makes that interface problematic?
> > >
> > > F
On Tuesday 10 April 2007, Jeff Garzik wrote:
> Thus, rather than forcing authors to make their code more complex, we
> should find another solution.
What about sth. like the "pre-forking" concept? So just have a thread creator
thread,
which checks the amount of unused threads and keeps them with
Defines the linker marcro EXTRA_RWDATA for marker data section. It
puts the marker data in a separate section that will not pollute the
normal .data section, which minimize the cache impact. Markers need such
a special section because they define a lot of spreaded and small data
structures at multi
Add EXTRA_RWDATA to alpha.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/alpha/kernel/vmlinux.lds.S
+++ b/arch/alpha/kernel/vmlinux.lds.S
@@ -90,6 +90,7 @@ SECTIONS
_data = .;
.data : {/* Data */
*(.data)
+ EXTRA_RWDATA
Add EXTRA_RWDATA to arm.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/arm/kernel/vmlinux.lds.S
+++ b/arch/arm/kernel/vmlinux.lds.S
@@ -155,6 +155,7 @@ SECTIONS
* and the usual data section
*/
*(.data)
+ EXTRA_RWDAT
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
> Jeremy Fitzhardinge wrote:
> >Why not submit a patch to do what you need here? (The Geode comment is
> >a bit worrying though.)
>
> Why should VMI add workaround into PIT code?
I'm not sure it's a workaround, seems more like a subtle diff (perhaps
it
Add EXTRA_RWDATA to arm26.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/arm26/kernel/vmlinux-arm26-xip.lds.in
+++ b/arch/arm26/kernel/vmlinux-arm26-xip.lds.in
@@ -112,6 +112,7 @@ SECTIONS
* and the usual data section
*/
*(.data)
Add EXTRA_RWDATA to avr32.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/avr32/kernel/vmlinux.lds.c
+++ b/arch/avr32/kernel/vmlinux.lds.c
@@ -107,6 +107,7 @@ SECTIONS
/* And the rest... */
*(.data.rel*)
*(.data)
+ EXT
David Lang wrote:
> On Wed, 11 Apr 2007, Stefan Richter wrote:
>> - with make xconfig: OK
>> - with make gconfig: OK
>> - with make menuconfig: less so, because:
>> When one switches a menuconfig _on_, one might miss that there are
>> subsequent options to configure. (Although the availability
Add EXTRA_RWDATA to cris.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/cris/arch-v10/vmlinux.lds.S
+++ b/arch/cris/arch-v10/vmlinux.lds.S
@@ -45,6 +45,7 @@ SECTIONS
__Sdata = . ;
.data : { /* Data */
*(.data)
+ E
Add EXTRA_RWDATA to frv.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/frv/kernel/vmlinux.lds.S
+++ b/arch/frv/kernel/vmlinux.lds.S
@@ -137,6 +137,7 @@ SECTIONS
.data : {/* Data */
*(.data .data.*)
*(.exit.data)
+ EXTRA_RWDATA
Add EXTRA_RWDATA to h8300.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/h8300/kernel/vmlinux.lds.S
+++ b/arch/h8300/kernel/vmlinux.lds.S
@@ -105,7 +105,9 @@ SECTIONS
. = ALIGN(0x4) ;
*(.data)
. = ALIGN(0x4) ;
- *(.data.*)
+
Add EXTRA_RWDATA to i386.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/i386/kernel/vmlinux.lds.S
+++ b/arch/i386/kernel/vmlinux.lds.S
@@ -78,6 +78,7 @@ SECTIONS
. = ALIGN(4096);
.data : AT(ADDR(.data) - LOAD_OFFSET) { /* Data */
*(.data)
+ EXTRA_RWDATA
Add EXTRA_RWDATA to ia64.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/ia64/kernel/vmlinux.lds.S
+++ b/arch/ia64/kernel/vmlinux.lds.S
@@ -214,7 +214,7 @@ SECTIONS
data : { } :data
.data : AT(ADDR(.data) - LOAD_OFFSET)
- { *(.data) *(.data1) *(.gnu.linkonce.d*) CON
Add EXTRA_RWDATA to m32r.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/m32r/kernel/vmlinux.lds.S
+++ b/arch/m32r/kernel/vmlinux.lds.S
@@ -51,6 +51,7 @@ SECTIONS
*(.spu)
*(.spi)
*(.data)
+ EXTRA_RWDATA
CONSTRUCTORS
}
--
Mathieu De
Add EXTRA_RWDATA to m68k.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/m68k/kernel/vmlinux-std.lds
+++ b/arch/m68k/kernel/vmlinux-std.lds
@@ -29,6 +29,7 @@ SECTIONS
.data : {/* Data */
*(.data)
+ EXTRA_RWDATA
CONSTRUCTORS
}
Eric W. Biederman wrote:
> Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
>
>
>> Let's allow page-alignment in general for per-cpu data (wanted by Xen, and
>> Ingo suggested KVM as well).
>>
>> Because larger alignments can use more room, we increase the max per-cpu
>> memory to 64k rather than
Add EXTRA_RWDATA to mips.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/mips/kernel/vmlinux.lds.S
+++ b/arch/mips/kernel/vmlinux.lds.S
@@ -64,6 +64,8 @@ SECTIONS
*(.data)
+EXTRA_RWDATA
+
CONSTRUCTORS
}
_gp = . + 0x8000;
--
Mathieu Desnoyers
Computer Engi
Add EXTRA_RWDATA to parisc.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/parisc/kernel/vmlinux.lds.S
+++ b/arch/parisc/kernel/vmlinux.lds.S
@@ -92,6 +92,7 @@ SECTIONS
. = ALIGN(L1_CACHE_BYTES);
.data : {/* Data */
*(.data)
+ EXTRA_RWDATA
Add EXTRA_RWDATA to powerpc.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/powerpc/kernel/vmlinux.lds.S
+++ b/arch/powerpc/kernel/vmlinux.lds.S
@@ -170,11 +170,13 @@ SECTIONS
*(.data)
*(.sdata)
*(.got.plt) *(.got)
+ E
Add EXTRA_RWDATA to ppc.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/ppc/kernel/vmlinux.lds.S
+++ b/arch/ppc/kernel/vmlinux.lds.S
@@ -73,6 +73,7 @@ SECTIONS
*(.sdata2)
*(.got.plt) *(.got)
*(.dynamic)
+EXTRA_RWDATA
CONSTRUCTORS
}
--
Mathieu Desnoye
Add EXTRA_RWDATA to s390.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/s390/kernel/vmlinux.lds.S
+++ b/arch/s390/kernel/vmlinux.lds.S
@@ -49,6 +49,7 @@ SECTIONS
.data : {/* Data */
*(.data)
+ EXTRA_RWDATA
CONSTRUCTORS
}
-
Add EXTRA_RWDATA to m68knommu.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/m68knommu/kernel/vmlinux.lds.S
+++ b/arch/m68knommu/kernel/vmlinux.lds.S
@@ -134,6 +134,7 @@ SECTIONS {
. = ALIGN(4);
_sdata = . ;
*(.data)
+
Add EXTRA_RWDATA to sh.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/sh/kernel/vmlinux.lds.S
+++ b/arch/sh/kernel/vmlinux.lds.S
@@ -40,6 +40,7 @@ SECTIONS
.data : {/* Data */
*(.data)
+ EXTRA_RWDATA
/* Align the initial ramdisk
Add EXTRA_RWDATA to sh64.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/sh64/kernel/vmlinux.lds.S
+++ b/arch/sh64/kernel/vmlinux.lds.S
@@ -79,6 +79,7 @@ SECTIONS
.data : C_PHYS(.data) { /* Data */
*(.data)
+ EXTRA_RWDATA
CONSTRUCTO
Add EXTRA_RWDATA to sparc.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/sparc/kernel/vmlinux.lds.S
+++ b/arch/sparc/kernel/vmlinux.lds.S
@@ -23,6 +23,7 @@ SECTIONS
.data:
{
*(.data)
+EXTRA_RWDATA
CONSTRUCTORS
}
.data1 : { *(.data1) }
--
Mathieu
Add EXTRA_RWDATA to sparc64.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/sparc64/kernel/vmlinux.lds.S
+++ b/arch/sparc64/kernel/vmlinux.lds.S
@@ -28,6 +28,7 @@ SECTIONS
.data:
{
*(.data)
+EXTRA_RWDATA
CONSTRUCTORS
}
.data1 : { *(.data1) }
--
Ma
Add EXTRA_RWDATA to um.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/um/kernel/dyn.lds.S
+++ b/arch/um/kernel/dyn.lds.S
@@ -98,6 +98,7 @@ SECTIONS
. = ALIGN(KERNEL_STACK_SIZE); /* init_task */
*(.data.init_task)
*(.data .data.* .gnu.linkonce.d.*)
+
Add EXTRA_RWDATA to v850.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/v850/kernel/vmlinux.lds.S
+++ b/arch/v850/kernel/vmlinux.lds.S
@@ -116,6 +116,7 @@
*(.data) \
*(.exit.data) /* 2
Add EXTRA_RWDATA to xtensa.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/xtensa/kernel/vmlinux.lds.S
+++ b/arch/xtensa/kernel/vmlinux.lds.S
@@ -144,7 +144,7 @@ SECTIONS
_fdata = .;
.data :
{
-*(.data) CONSTRUCTORS
+*(.data) EXTRA_RWDATA CONSTRUCTORS
. = AL
Add EXTRA_RWDATA to x86_64.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/x86_64/kernel/vmlinux.lds.S
+++ b/arch/x86_64/kernel/vmlinux.lds.S
@@ -59,6 +59,7 @@ SECTIONS
/* Data */
.data : AT(ADDR(.data) - LOAD_OFFSET) {
*(.data)
+
[1] kernel errors reporting unaligned access of memory
[2] The following two lines iterate twice a piece, about once every 2 minutes:
Kernel unaligned access at TPC[79c344] arpt_do_table+0x3cc/0x640
Kernel unaligned access at TPC[79c33c] arpt_do_table+0x3c4/0x640
[3] ...
[4] Linux
Chris Wright wrote:
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
Yes, but unfortunately that is a nop:
/*
* Avoid unnecessary state transitions, as it confuses
* Geode / Cyrix based boxen.
*/
case CLOCK_EVT_MODE_SHUTDOWN:
if (evt->mod
Hi Rudolf,
On 4/10/07, Rudolf Marek <[EMAIL PROTECTED]> wrote:
Hello all,
First I would like to thank Jean for his great work even if could be seen as
"slow". He did the perfect job, allowing only just perfect code to enter the
trees.
I completely agree.
> I haven't seen anything from Rudo
Please report sparc platform bugs to sparclinux@vger.kernel.org next
time, thank you.
Meanwhile I'll take a look at this one.
-
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/majo
Hello David,
Monday, April 9, 2007, 11:22:25 PM, you wrote:
> On Monday 09 April 2007 10:18 am, Paul Sokolovsky wrote:
>> > Nobody who really wants to have such an implementation framework has yet
>> > ponied up and done the work to make one.
>>
>> Well, sorry if it wasn't made clear, but we
Documents the linux/marker.h header. Fix a bitwise flag manipulation mistake
in the MARK_GENERIC macro.
Use the __marker (ro), new __marker_strings (ro) and __marker_data (rw)
sections. It depends on the linker modification which defines this last
section.
It allows the use of a probe "private" d
Quoting Oleg Nesterov ([EMAIL PROTECTED]):
> 1. rename reparent_to_init() to reparent_kthread() and export it
>
> 2. use init_pid_ns.child_reaper instead of child_reaper(current)
Each of these patches looks good to me, but this part in particular
is a must-have bugfix.
Just started some tests, i
On Wed, Apr 11, 2007 at 12:09:01AM +0200, Jan Engelhardt wrote:
>
> On Apr 11 2007 00:04, Stefan Richter wrote:
> >
> >[...] I tried one of the patches
> > - with make xconfig: OK
> > - with make gconfig: OK
> > - with make menuconfig: less so, because:
> >When one switches a menuconfig _on_, o
Document the i386 marker header, change it to use the __marker,
__marker_data and __marker_strings sections. Change the flag usage to
use MF_* directly (which is now a bitmask). In marker.c, for the i386
optimized marker enabling, check the a simple test is the value will be
changed. If not, simply
Changes to the powerpc marker header : Use the new MF_* bitmask, use the
__markers, __markers_data and __markers_strings sections, add
documentation.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/include/asm-powerpc/marker.h
+++ b/include/asm-powerpc/marker.h
@@ -1,3 +1,6 @@
+#ifndef
Add alpha marker.h, add arm26 marker.h, use the new MF_* bitmask for
asm-generic/marker.h. Document asm-generic/marker.h.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- /dev/null
+++ b/include/asm-alpha/marker.h
@@ -0,0 +1,13 @@
+/*
+ * marker.h
+ *
+ * Code markup for dynamic and stat
Here is a trivial conversion of the h8300 arch to the GENERIC_TIME
infrastructure (h8300 does not have better then jiffies resolution, so
there are no clocksources to add). I have not tested this at all, but it
seems pretty straight forward
I'd appreciate any comments or feedback!
thanks
-john
Update marker Documentation to be in sync with the flag bitmask
change. Give more complete probe example.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/Documentation/marker.txt
+++ b/Documentation/marker.txt
@@ -12,11 +12,11 @@ probe module examples. This is what connects to a marker
Add Instrumentation/markers menus to avr32.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/arch/avr32/Kconfig.debug
+++ b/arch/avr32/Kconfig.debug
@@ -6,6 +6,9 @@ config TRACE_IRQFLAGS_SUPPORT
source "lib/Kconfig.debug"
+menu "Instrumentation Support"
+ depends on EXPERIMEN
Add documentation to the module.c marker functions. Update them to
follow the flags modifications.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -303,24 +303,36 @@ static struct module *find_module(const char *name)
}
#ifdef CONFIG_MARKERS
On Saturday 07 April 2007 1:08 pm, David Brownell wrote:
> By adding a warning over this create-links patch, I found that the
> system in the $SUBJECT patch (and likely every ACPI system) has
> two different nodes that correspond to one ACPI node:
>
> /sys/devices/pci:00 ... pci root no
Here is a trivial conversion of the v850 arch to the GENERIC_TIME
infrastructure. While the v850 does not currently have better then
jiffies resolution, it does have some #if 0'ed infrastructure that looks
like its being implemented, however I've not seen anything for a few
months.
I have not tes
The RAID card in question has reported an "SPD CheckSum Error" (bad
ram?) during system power on so it's looking like this is probably a
hardware or firmware problem and not a driver issue.
-J
--
On Tue, Apr 03, 2007 at 08:45:38AM -0700, Randy Dunlap wrote:
> On Mon, 2 Apr 2007 17:21:35 -1000 Jos
Here's a patch for kernel-doc that enables the generation of a global, TOC-like
index.html
page after building 'htmldocs'
Signed-off-by: Borislav Petkov <[EMAIL PROTECTED]>
Index: 21-rc6/Documentation/DocBook/Makefile
===
--- 21-r
On 11 Apr 2007 00:56:51 +0200
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Jan Kara <[EMAIL PROTECTED]> writes:
>
> > Hello!
> >
> > In thread http://lkml.org/lkml/2007/3/9/403, we discussed a problem
> > with the current heuristic for detecting sequential IO in
> > do_generic_mapping_read() - fo
On Tue, Apr 10, 2007 at 08:36:56AM +0200, Ingo Molnar wrote:
> the runqueue is really supposed to be cacheline-isolated at _both_ ends
> - at its beginning and at its end as well.
Then either we need to define the first element in the struct as
cacheline aligned or move into section where all the
This is difficult.
Summary of problem is:
Filesystem on LVM on md/raid1
Add an md/linear to the md/raid1 and fs dies with 'bio too big'.
Where to begin
The fs level builds bios to send down to the device, and it queries
the device to find out how big the bio can be.
There are two ways i
On Tue 10 Apr 2007 08:55, David Howells pondered:
> Looking at alloc_pg_vec() in af_packet.c, I will place my bets on the
> latter case. I don't know that this is a problem; it depends on how things
> work, and that I don't know offhand. If someone can give me a simple test
> program, I would be
Resurrect an old patch that uses atomic operation to update ring buffer
index on AIO event queue. This work allows futher application/libaio
optimization to run fast path io_getevents in user space.
I've also added one more change on top of old implementation that rounds
ring buffer size to power
On Tue, 2007-04-10 at 15:20 -0700, Venki Pallipadi wrote:
> On Mon, Apr 09, 2007 at 07:40:52PM +0200, Rafael J. Wysocki wrote:
> > On Monday, 9 April 2007 18:14, Pallipadi, Venkatesh wrote:
> > >
> > > >-Original Message-
> > > >From: Rafael J. Wysocki [mailto:[EMAIL PROTECTED]
> > > >Sen
On Tuesday 10 April 2007 4:29 pm, David Brownell wrote:
> ... the appended
> patch goes on top of the previous pnpacpi patch, and should (nyet tested!)
> fix another place I saw that warning.
And here's a tested version. Curiouser and curiouser. I think the mapping
of ACPI tables to sysfs
On Tue, Apr 10, 2007 at 07:59:29PM -0400, Adam Belay wrote:
> On Tue, 2007-04-10 at 15:20 -0700, Venki Pallipadi wrote:
> > On Mon, Apr 09, 2007 at 07:40:52PM +0200, Rafael J. Wysocki wrote:
> > > On Monday, 9 April 2007 18:14, Pallipadi, Venkatesh wrote:
> > > >
> > > > >-Original Message
On Wed, 2007-04-11 at 08:33 +1000, Neil Brown wrote:
> A READDIR (aka getdents2) should take a directory handle, a cookie,
> and a filename, and should return filenames and cookies. The
> cookies may all be identical or may not. The filename might be used
> by the filesystem, or it might
it looks ok, but I have several questions:
1. why should we bind this to platform_device, what if the gpio device
is not actually a "platform_device", say, a I2C device, a SPI device or
even a USB device?
2. I still doubt the benefit of using of a structure for a gpio, isn't a gpio
number not en
> Is there any chance of getting a fix for the use-after-free that can
> be caused by allocating something from userspace, failing to mmap the
> buffer and then exiting? To see what happens, look at how
> ipath_create_cq sticks a struct ipath_mmap_info into the pending mmap
> "list" (and yes
Hi Andrew,
I get the following compiler error when building 2.6.21-rc6-mm1 for
m68k:
/opt/crosstool/gcc-4.1.1-glibc-2.3.6/m68k-unknown-linux-gnu/bin/m68k-unknown-linux-gnu-gcc
-Wp,-MD,arch/m68k/kernel/.asm-offsets.s.d -nostdinc -isystem
/opt/crosstool/gcc-4.1.1-glibc-2.3.6/m68k-unknown-lin
Hi Andrew,
I get the following error when compiling 2.6.21-rc6-mm1 for MIPS :
/opt/crosstool/gcc-3.4.5-glibc-2.3.6/mips-unknown-linux-gnu/bin/mips-unknown-linux-gnu-gcc
-Wp,-MD,arch/mips/sgi-ip22/.ip22-time.o.d -nostdinc -isystem
/opt/crosstool/gcc-3.4.5-glibc-2.3.6/mips-unknown-linux-gnu/
Hi Andrew,
I get the following build error on sparc :
/opt/crosstool/gcc-4.1.1-glibc-2.3.6/sparc-unknown-linux-gnu/bin/sparc-unknown-linux-gnu-gcc
-Wp,-MD,arch/sparc/kernel/.irq.o.d -nostdinc -isystem
/opt/crosstool/gcc-4.1.1-glibc-2.3.6/sparc-unknown-linux-gnu/lib/gcc/sparc-unknown-linux-g
Hi Andrew,
I get the following build error when building 2.6.21-rc6-mm1 for
sparc64:
/opt/crosstool/gcc-3.4.5-glibc-2.3.6/sparc64-unknown-linux-gnu/bin/sparc64-unknown-linux-gnu-gcc
-Wp,-MD,arch/sparc64/kernel/.traps.o.d -nostdinc -isystem
/opt/crosstool/gcc-3.4.5-glibc-2.3.6/sparc64-unknow
Hi Andrew,
I get the following build error when building 2.6.21-rc6-mm1 for ppc
405:
/opt/crosstool/gcc-4.1.1-glibc-2.3.6/powerpc-405-linux-gnu/bin/powerpc-405-linux-gnu-gcc
-m32 -Wp,-MD,arch/ppc/syslib/.ppc4xx_sgdma.o.d -nostdinc -isystem
/opt/crosstool/gcc-4.1.1-glibc-2.3.6/powerpc-405-l
301 - 400 of 490 matches
Mail list logo