From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752169AbcDWTgN (ORCPT ); Sat, 23 Apr 2016 15:36:13 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:39158 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751829AbcDWTgM (ORCPT ); Sat, 23 Apr 2016 15:36:12 -0400 Date: Sat, 23 Apr 2016 21:36:08 +0200 From: Pavel Machek To: Sergey Senozhatsky Cc: Andrew Morton , Jan Kara , Petr Mladek , Tejun Heo , Tetsuo Handa , linux-kernel@vger.kernel.org, Byungchul Park , Sergey Senozhatsky Subject: Re: [RFC][PATCH v4 0/2] printk: Make printk() completely async Message-ID: <20160423193608.GA15755@amd> References: <1457964820-4642-1-git-send-email-sergey.senozhatsky@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1457964820-4642-1-git-send-email-sergey.senozhatsky@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 2016-03-14 23:13:38, Sergey Senozhatsky wrote: > Hello, > > RFC > > The patch set is based on slightly updated Jan Kara's patches. > > This patch set makes printk() completely asynchronous: new messages > are getting upended to the kernel printk buffer, but instead of 'direct' > printing the actual print job is performed by a dedicated kthread. > This has the advantage that printing always happens from a schedulable > context and thus we don't lockup any particular CPU or even > interrupts. And that means that printk() will become mostly useless for debugging, right? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html