From: Scott Wood <scottwood@freescale.com>
To: Vineeth <vneethv@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-embedded@vger.kernel.org
Subject: Re: Timer interrupt on Linux 3.0.3
Date: Fri, 16 Sep 2011 12:03:40 -0500 [thread overview]
Message-ID: <4E73816C.6000304@freescale.com> (raw)
In-Reply-To: <CAFbQSaD-c=QqSsq__VtBEcMCJabnBi4AP4KunDNV7u7xXAuaTw@mail.gmail.com>
On 09/16/2011 06:43 AM, Vineeth wrote:
> Hi,
>
> We are porting Linux on MPC7410 based board. As there was some issue
> with the processor DECrementer and timebase registers,
What was the issue? You really should try to make this work rather than
hack around it.
> lately we moved to Linux 3.0.3. What we found was even without a proper
> timer, the kernel with initramfs worked (except the calls like
> sleep,delay ofcourse); Is there any major difference in the scheduler ?
> or the way context switch happens ? is it not depended on the timer
> interrupt or the timer ??
If your timer is broken then you won't get timeslice expiration, but
basic scheduling should still work. Most scheduling (depending on type
of load, of course) will be triggered by processes blocking or being
woken up by I/O, not timeslice expiration.
-Scott
next prev parent reply other threads:[~2011-09-16 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 11:43 Timer interrupt on Linux 3.0.3 Vineeth
2011-09-16 17:03 ` Scott Wood [this message]
2011-09-21 6:56 ` Vineeth
2011-09-21 19:41 ` Scott Wood
2011-09-22 6:22 ` MohanReddy koppula
2011-09-26 9:11 ` Vineeth
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=4E73816C.6000304@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vneethv@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).