From: "Codrin Alexandru Grajdeanu" <grcodal@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Octavian Purdila <tavi@cs.pub.ro>
Subject: Interrupt context
Date: Sun, 23 Mar 2008 23:44:56 +0200 [thread overview]
Message-ID: <3581ed890803231444i58cff10i408dc4d9bef7b184@mail.gmail.com> (raw)
Hi all,
I am a student from Politehnica University of Bucharest studying
Computer Science. I would like to add some new kernel source checks
based on sparse. The first idea would be to test if from interrupt
context sleepy functions are called.
To test this, sparse would be required to run twice. First to get all
interrupt context functions, by verifying what arguments are passed to
irq_handler_t() and what values are passed to the function pointers in
struct timer_list, softirq_action and tasklet_struct. The second run
would generate the call graph for this function and would verify if
schedule() is called inside their call graph.
What do you think about this?
Thank you,
Codrin Grajdenau
next reply other threads:[~2008-03-23 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 21:44 Codrin Alexandru Grajdeanu [this message]
2008-03-24 21:00 ` Interrupt context Christopher Li
2008-03-25 1:34 ` Octavian Purdila
2008-03-25 2:57 ` Christopher Li
2008-03-26 12:43 ` Octavian Purdila
2008-03-26 21:53 ` Christopher Li
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=3581ed890803231444i58cff10i408dc4d9bef7b184@mail.gmail.com \
--to=grcodal@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=tavi@cs.pub.ro \
/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).