mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David <david@livux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8,v2.6.22.13, v2.6.21.7
Date: Tue, 20 Nov 2007 07:13:02 +0100	[thread overview]
Message-ID: <20071120061302.GH20436@elte.hu> (raw)
In-Reply-To: <200711192239.51301.david@livux.com>


* David <david@livux.com> wrote:

> El Lunes, 19 de Noviembre de 2007, Ingo Molnar escribió:
> > * David <david@livux.com> wrote:
> > > I have removed all other patches, and applied only cfs v24 above
> > > 2.6.23.8, and the compiler ran into (with CONFIG_FAIR_GROUP_SCHED
> > > enabled):
> >
> > does the patch below help?
> >
> > 	Ingo
> 
> Yes, now sched.c compile without errors, but linking fails at:
> 
> 
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> kernel/built-in.o:(.data+0x4a8): undefined reference to `sysctl_sched_min_bal_int_shares'
> kernel/built-in.o:(.data+0x4d4): undefined reference to `sysctl_sched_max_bal_int_shares'
> make: *** [.tmp_vmlinux1] Error 1

does the patch below do the trick?

	Ingo

Index: linux/kernel/sysctl.c
===================================================================
--- linux.orig/kernel/sysctl.c
+++ linux/kernel/sysctl.c
@@ -309,7 +309,7 @@ static struct ctl_table kern_table[] = {
 		.mode		= 644,
 		.proc_handler	= &proc_dointvec,
 	},
-#ifdef CONFIG_FAIR_GROUP_SCHED
+#if defined(CONFIG_FAIR_GROUP_SCHED) && defined(CONFIG_SMP)
 	{
 		.ctl_name	= CTL_UNNUMBERED,
 		.procname	= "sched_min_bal_int_shares",

  reply	other threads:[~2007-11-20  6:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 18:25 David
2007-11-19 18:57 ` Ingo Molnar
2007-11-19 19:51   ` David
2007-11-19 20:44     ` Ingo Molnar
2007-11-19 20:50     ` Ingo Molnar
2007-11-19 21:39       ` David
2007-11-20  6:13         ` Ingo Molnar [this message]
2007-11-20  9:23           ` David
  -- strict thread matches above, loose matches on Subject: below --
2007-11-23  8:23 [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7 Durand
2007-11-23 12:23 ` Ingo Molnar
2007-11-23 16:44   ` Durand
2007-11-20 22:48 Matthew
2007-11-20 22:59 ` Ingo Molnar
2007-11-19 15:17 Ingo Molnar
2007-11-19 16:04 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8,v2.6.22.13, v2.6.21.7 Fortier,Vincent [Montreal]
2007-11-19 18:59   ` Ingo Molnar
2007-11-19 18:12 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7 Erik Andersen
2007-11-19 18:52   ` Ingo Molnar
2007-11-19 19:24     ` Erik Andersen
2007-11-19 19:46     ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3,v2.6.23.8, " Fortier,Vincent [Montreal]
2007-11-20 11:24 ` [patch/backport] CFS scheduler, -v24, for v2.6.24-rc3, v2.6.23.8, " Damien Wyart
2007-11-20 12:41   ` Srivatsa Vaddagiri
2007-11-20 12:55   ` Ingo Molnar
2007-11-20 13:22     ` Damien Wyart
2007-11-20 20:00 ` Vincent Fortier
2007-11-20 20:38 ` Fabio Comolli
2007-11-20 20:41   ` Ingo Molnar
2007-11-20 20:47     ` Fabio Comolli
2007-11-20 21:53       ` Ingo Molnar
2007-11-21  8:50         ` Fabio Comolli
2007-11-21 10:39           ` Ingo Molnar
2007-11-21 11:11             ` Fabio Comolli

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=20071120061302.GH20436@elte.hu \
    --to=mingo@elte.hu \
    --cc=david@livux.com \
    --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

all inboxes | Powered by JetHome®