2002-07-14 21:07:56

by Robert Love

[permalink] [raw]
Subject: [PATCH] preemptive kernel for 2.4.19-rc1-ac3

A preempt-kernel patch for 2.4.19-rc1-ac3 is available at:

ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.19-rc1-ac3-1.patch

and mirrors.

The recent scheduler bits introduced plenty of changes to cause the
patch to fail to apply.

This new preempt-kernel patch also includes some of the
scheduler-related preemption optimizations found in 2.5.

Robert Love


2002-07-15 00:41:07

by Ed Tomlinson

[permalink] [raw]
Subject: Re: [PATCH] preemptive kernel for 2.4.19-rc1-ac3

If you build with preempt=N (for the scheduler stuff) the link of the
kernel fails.

kernel/kernel.o: In function `sys_sched_yield':
kernel/kernel.o(.text+0x1154): undefined reference to
`spin_unlock_no_resched'

Ed Tomlinson

make: *** [vmlinux] Error 1


Robert Love wrote:

> A preempt-kernel patch for 2.4.19-rc1-ac3 is available at:
>
>
ftp://ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.19-rc1-ac3-1.patch
>
> and mirrors.
>
> The recent scheduler bits introduced plenty of changes to cause the
> patch to fail to apply.
>
> This new preempt-kernel patch also includes some of the
> scheduler-related preemption optimizations found in 2.5.
>
> Robert Love
>
> -
> 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/

2002-07-15 16:33:15

by Robert Love

[permalink] [raw]
Subject: Re: [PATCH] preemptive kernel for 2.4.19-rc1-ac3

On Sun, 2002-07-14 at 17:43, Ed Tomlinson wrote:

> If you build with preempt=N (for the scheduler stuff) the link of the
> kernel fails.

What, someone does not use preemption? 8)

An updated patch is available:

http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.19-rc1-ac3-2.patch

I missed the definition of the new spin_unlock_no_resched from 2.5 in
the !CONFIG_PREEMPT case. Thank you for pointing this out.

Robert Love