From: Ralf Baechle <ralf@linux-mips.org>
To: fpga dsp <fpga_dsp@yahoo.com.au>
Cc: linux-mips@linux-mips.org
Subject: Re: schedule() and mipsel processor
Date: Sun, 29 Jun 2003 19:35:23 +0200 [thread overview]
Message-ID: <20030629173522.GC9469@linux-mips.org> (raw)
In-Reply-To: <20030628025749.40346.qmail@web41205.mail.yahoo.com>
On Sat, Jun 28, 2003 at 12:57:49PM +1000, fpga dsp wrote:
> I may ask a stupid question here but I have problem of calling any functions such as interruptible_sleep_on_timeout, sleep_on ... in a timer handler, the kernel just crash straight away in the function schedule(). Now I go and do a diff between kern/sched.c on i686 source and mipsel source. clearly , they are different. So the question is from kernel programming point of view, the bottom-half of interrupt handler is still considered interrupt handler? I don't see any platform dependent code in the scheduler at all. So why a mips scheduler is different from intel scheduler ?
Bs. There was no need to change kernel/sched.c at all so you're probably
simply diffing the wrong versions.
Ralf
next prev parent reply other threads:[~2003-06-29 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 2:57 schedule() and mipsel processor fpga dsp
2003-06-29 17:35 ` Ralf Baechle [this message]
2003-06-30 17:00 ` Jun Sun
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=20030629173522.GC9469@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=fpga_dsp@yahoo.com.au \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.