Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Peter Zijlstra <a.p.zijlstra <at> chello.nl>
Subject: [RFC][PATCH 0/7] improve printk reliability
Newsgroups: gmane.linux.kernel
Date: Wednesday 21st December 2011 10:57:39 UTC (over 5 years ago)
Hi,

So these are my current efforts to make my own console output more
reliable. I've hit every deadlock described in this series and a few
more.

With these patches applied I can printk() and WARN() from inside 
scheduler context and not have my machine deadlock, even without the 
aid of early_printk().

While I'll go an remove the sole printk() I found in the scheduler
so that we don't have to rely on the console doing this, it is good
to have a reliable console that can do this.

As it stands some of the patches, the semaphore one in particular,
are really too ugly to live so I won't push those but wanted to share
anyway.

Debugging this was 'fun', and I really hope to not have to do it
again :-)
 
CD: 3ms