From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S965695AbdCVSmK (ORCPT <rfc822;w@1wt.eu>);
        Wed, 22 Mar 2017 14:42:10 -0400
Received: from bombadil.infradead.org ([65.50.211.133]:43387 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751109AbdCVSmG (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 22 Mar 2017 14:42:06 -0400
Date: Wed, 22 Mar 2017 18:59:20 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Petr Mladek <pmladek@suse.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        "Rafael J . Wysocki" <rjw@rjwysocki.net>, linux-kernel@vger.kernel.org,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [RFC][PATCH 0/4] printk: introduce printing kernel thread
Message-ID: <20170322175920.bcltzwega6dts2n4@hirez.programming.kicks-ass.net>
References: <20170306124554.828-1-sergey.senozhatsky@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170306124554.828-1-sergey.senozhatsky@gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Mar 06, 2017 at 09:45:50PM +0900, Sergey Senozhatsky wrote:
>  sysrq is potentially even trickier. can we always wake_up() kernel
>  thread from sysrq? there probably might be cases when we can't rely
>  on the scheduler.

sysrq runs from interrupt context, right? Should be able to do wakeups.