From: Ingo Molnar <mingo@elte.hu>
To: "S.Çağlar Onur" <caglar@pardus.org.tr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20
Date: Wed, 26 Sep 2007 15:48:00 +0200 [thread overview]
Message-ID: <20070926134800.GA6220@elte.hu> (raw)
In-Reply-To: <200709261633.24283.caglar@pardus.org.tr>
* S.Çağlar Onur <caglar@pardus.org.tr> wrote:
> Compilation [against 2.6.20.20] fails with
>
> buildfarm linux-2.6.20 # make
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CHK include/linux/compile.h
> CC kernel/sched.o
> In file included from kernel/sched.c:850:
> kernel/sched_fair.c:49: error: sysctl_sched_nr_latency causes a section type
> conflict
> make[1]: *** [kernel/sched.o] Error 1
> make: *** [kernel] Error 2
oops, indeed! This happens with certain .config combinations only and it
didnt trigger on mine.
> @kernel/sched_fair.c
> -const_debug unsigned int sysctl_sched_nr_latency __read_mostly = 20;
> +const_debug unsigned int sysctl_sched_nr_latency = 20;
>
> seems solve that issue but i'm not sure this is the right thing to do
> or not :)
your fix is the right one - and i've updated the patches with this small
fix. Anyone who hits this issue should re-download the same patch once
more, or should apply the small patch below.
Ingo
Index: linux/kernel/sched_fair.c
===================================================================
--- linux.orig/kernel/sched_fair.c
+++ linux/kernel/sched_fair.c
@@ -46,7 +46,7 @@ const_debug unsigned int sysctl_sched_ch
* Minimal preemption granularity for CPU-bound tasks:
* (default: 2 msec, units: nanoseconds)
*/
-const_debug unsigned int sysctl_sched_nr_latency __read_mostly = 20;
+const_debug unsigned int sysctl_sched_nr_latency = 20;
/*
* sys_sched_yield() compat mode
next prev parent reply other threads:[~2007-09-26 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 11:13 [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20 Ingo Molnar
2007-09-26 13:33 ` S.Çağlar Onur
2007-09-26 13:48 ` Ingo Molnar [this message]
2007-09-28 20:26 ` Alejandro Riveira Fernández
2007-09-29 2:20 ` Henrique de Moraes Holschuh
2007-09-29 16:51 ` Alejandro Riveira Fernández
2007-09-30 15:26 ` Ingo Molnar
2007-10-02 18:12 ` Alejandro Riveira Fernández
2007-10-26 18:56 ` [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8,v2.6.21.7, v2.6.20.20 Fortier,Vincent [Montreal]
-- strict thread matches above, loose matches on Subject: below --
2007-09-29 11:11 [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20 Matthew
2007-09-30 15:43 ` Ingo Molnar
[not found] ` <e85b9d30709300943rded9801xddc6ca0a4773ff53@mail.gmail.com>
2007-09-30 17:27 ` Ingo Molnar
2007-09-30 23:54 ` Bill Davidsen
2007-10-02 9:06 ` Matthew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070926134800.GA6220@elte.hu \
--to=mingo@elte.hu \
--cc=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox