From: sumedh tirodkar <sumedhtirodkar@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Problem with decrementer interrupt
Date: Mon, 23 Feb 2009 13:24:32 +0530 [thread overview]
Message-ID: <d2b9ccd90902222354o2e42db77h2f86fda45b5483b6@mail.gmail.com> (raw)
In the handler for decrementer interrupt...there is a call to a C function...
Now if the call is removed...the decrementer interrupt works perfectly fine...
But if the C function is present, then the decrementer interrupt stops
coming after say 5-6 times...
Not able to find any reasoning for the same...
Has anyone come across this kind of problem?If yes, am i missing something?
Regards,
Sumedh
next reply other threads:[~2009-02-23 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 7:54 sumedh tirodkar [this message]
[not found] ` <85a5c2010902230439n1096196dr519462513bc3910d@mail.gmail.com>
2009-02-23 13:03 ` Problem with decrementer interrupt sumedh tirodkar
2009-02-23 14:48 ` Matt Gessner
2009-02-23 17:04 ` sumedh tirodkar
2009-02-23 17:33 ` sjoyeau
2009-02-23 18:02 ` sumedh tirodkar
2009-02-24 7:54 ` sjoyeau
2009-02-24 11:53 ` sumedh tirodkar
2009-02-24 17:32 ` sumedh tirodkar
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=d2b9ccd90902222354o2e42db77h2f86fda45b5483b6@mail.gmail.com \
--to=sumedhtirodkar@gmail.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).