From: Dinesh Ahuja <mdlinux7@yahoo.co.in>
To: linux-kernel@vger.kernel.org
Subject: Accessing runqueue from device driver
Date: Sat, 15 Jan 2005 11:25:29 +0000 (GMT) [thread overview]
Message-ID: <20050115112529.9759.qmail@web8509.mail.in.yahoo.com> (raw)
Hi All,
I am visulaizing a one of the use of char device
driver.
I need to write a char device which will prompt me by
printing on my pseudo terminal if there is any zombie
element in a runqueue on a specific processor.
Is it possible to keep a track on runqueue through a
function defined in a char device ? If I provied the
information about zombies via /proc filesystem, then a
user needs to read file again and again and would not
be able to keep a constant watch on the zombies. Is it
possible that my char device goes to sleep on a
waitqueue and wakes up's only when a zombies process
is present in a runqueue and then after giving details
of that zombie process, my char device driver again
goes to sleep and wait for new zombies in a runqueue.
Could anyone guide me is the above thought can be
implemented.
Can anybody guide me that how to use this_rq in a
kernel module ? I get following error:
CharRunQueue.o: unresolved symbol this_rq
Including sched.h wonot help as macro is defined in
sched.c. If I include sched.c, then I get lots of
errors which are as follows:
CharRunQueue.o: unresolved symbol immediate_bh
CharRunQueue.o: unresolved symbol timer_bh
CharRunQueue.o: unresolved symbol __switch_to
CharRunQueue.o: unresolved symbol cpu_gdt_table
CharRunQueue.o: unresolved symbol __mmdrop
CharRunQueue.o: unresolved symbol tqueue_bh
CharRunQueue.o: unresolved symbol default_ldt
CharRunQueue.o: unresolved symbol show_trace_task
CharRunQueue.o: unresolved symbol init_timervecs
CharRunQueue.o: unresolved symbol __put_task_struct
Please let me know where I am going wrong.
Regards
Dinesh
________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
reply other threads:[~2005-01-15 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050115112529.9759.qmail@web8509.mail.in.yahoo.com \
--to=mdlinux7@yahoo.co.in \
--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
all inboxes | Powered by JetHome®