From: Jon Smirl <jonsmirl@yahoo.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Keith Packard <keithp@keithp.com>
Subject: Is it possible to implement interrupt time printk's reliably?
Date: Thu, 6 May 2004 19:52:52 -0700 (PDT) [thread overview]
Message-ID: <20040507025252.38914.qmail@web14929.mail.yahoo.com> (raw)
Problem:
1) Some operations on graphics cards cannot be stopped once they are started.
It's not reasonable to turn interrupts off around these operations.
2) Kernel developers want console printk's to work from interrupt routines.
How do you fix this situation?
1) Grpahics driver has started non-restartable operation. For example
transferring a bitmap. This is not an automatic DMA operation, CPU involvement
is needed.
2) Interrupt happens
3) Printk happens from interrupt.
Now we're stuck. The graphics chip is in a non-interruptible state and printk
wants to use it.
We need some mechanism to get back to the driver code and finish the
non-restartable operation before the printk can be allowed to proceed.
Another solution also comes to mind. Mark the appropriate sections in the video
driver with BEGIN/END_INT_PRINTK. Then add a kernel build option to convert
these macros to en/disable interrupts if interrupt time printk's are allowed.
Would it be acceptable to disable interrupts for signifcant time on a
development kernel where the developer is printk'ing from interrupts?
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
next reply other threads:[~2004-05-07 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 2:52 Jon Smirl [this message]
2004-05-07 5:17 ` Andrew Morton
2004-05-07 13:34 ` Jon Smirl
2004-05-07 19:13 ` Andrew Morton
2004-05-07 19:26 ` Jon Smirl
2004-05-07 20:01 ` Andrew Morton
2004-05-09 16:33 ` Jon Smirl
2004-05-10 21:55 ` James Simmons
2004-05-10 22:22 ` Jon Smirl
2004-05-11 0:23 ` James Simmons
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=20040507025252.38914.qmail@web14929.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=keithp@keithp.com \
--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®