From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Subject: Re: BFS v0.313 CPU scheduler for 2.6.32
Date: Wed, 30 Dec 2009 20:55:55 +0100 [thread overview]
Message-ID: <20091230195555.GA5367@fancy-poultry.org> (raw)
In-Reply-To: <200912301900.29578.mboton@gmail.com>
On 30.12.2009, Miguel Botón wrote:
> If you want to try BFS on a 2.6.33 kernel, you can try this 'unofficial' port:
> http://git.zen-kernel.org/?p=kernel/zen.git;a=shortlog;h=refs/heads/sched-bfs
> I'm currently using it with no issues so far.
Your patch applies cleanly to 2.6.33-rc2, but compilation fails:
[....]
In file included from kernel/sched.c:2:
kernel/sched_bfs.c: In function '__sched_setscheduler':
kernel/sched_bfs.c:3484: warning: passing argument 1 of 'spinlock_check' from incompatible pointer type
kernel/sched_bfs.c:3493: warning: passing argument 1 of 'spin_unlock_irqrestore' from incompatible pointer type
kernel/sched_bfs.c:3509: warning: passing argument 1 of 'spin_unlock_irqrestore' from incompatible pointer type
kernel/sched_bfs.c: In function 'sys_sched_yield':
kernel/sched_bfs.c:3846: warning: passing argument 1 of '_raw_spin_unlock' from incompatible pointer type
kernel/sched_bfs.c: At top level:
kernel/sched_bfs.c:6018: error: conflicting types for 'partition_sched_domains'
include/linux/sched.h:1025: error: previous declaration of 'partition_sched_domains' was here
kernel/sched_bfs.c: In function 'sched_init':
kernel/sched_bfs.c:6425: warning: passing argument 2 of 'plist_head_init' from incompatible pointer type
kernel/sched_bfs.c: In function 'normalize_rt_tasks':
kernel/sched_bfs.c:6499: warning: passing argument 1 of 'spinlock_check' from incompatible pointer type
kernel/sched_bfs.c:6513: warning: passing argument 1 of 'spin_unlock_irqrestore' from incompatible pointer type
make[1]: *** [kernel/sched.o] Error 1
make[1]: *** Waiting for unfinished jobs....
CC arch/x86/kernel/alternative.o
CC fs/open.o
[....]
[....]
CC arch/x86/kernel/init_task.o
LDS arch/x86/kernel/vmlinux.lds
CC [M] arch/x86/kernel/msr.o
CC [M] arch/x86/kernel/cpuid.o
CC [M] arch/x86/kernel/microcode_core.o
CC [M] arch/x86/kernel/microcode_amd.o
arch/x86/kernel/init_task.c:31: warning: missing braces around initializer
arch/x86/kernel/init_task.c:31: warning: (near initialization for 'init_task.pi_lock')
arch/x86/kernel/init_task.c:31: error: incompatible types in initialization
arch/x86/kernel/init_task.c:31: error: initializer element is not constant
arch/x86/kernel/init_task.c:31: error: (near initialization for 'init_task.dirties.lock')
arch/x86/kernel/init_task.c:31: error: initializer element is not constant
arch/x86/kernel/init_task.c:31: error: (near initialization for 'init_task.perf_event_mutex.wait_lock')
make[2]: *** [arch/x86/kernel/init_task.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [arch/x86/kernel] Error 2
make: *** [arch/x86] Error 2
liesel:/usr/src/linux-2.6.33-rc2 #
next prev parent reply other threads:[~2009-12-30 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 18:00 BFS v0.313 CPU scheduler for 2.6.32 Miguel Botón
2009-12-30 19:55 ` Heinz Diehl [this message]
2009-12-30 20:58 ` Miguel Botón
-- strict thread matches above, loose matches on Subject: below --
2009-12-30 12:34 Con Kolivas
2009-12-30 13:55 ` Thomas Backlund
2009-12-30 14:41 ` Con Kolivas
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=20091230195555.GA5367@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--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