Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp590953imm; Thu, 26 Jul 2018 08:40:06 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdOVt8jHQORE13gJIQQDaDYc851O6vnZJx2RXueVH4YTEH2H3wU07T3wswHZydLHz5eqlrB X-Received: by 2002:a63:a619:: with SMTP id t25-v6mr2402133pge.288.1532619606485; Thu, 26 Jul 2018 08:40:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532619606; cv=none; d=google.com; s=arc-20160816; b=MePa38PC8fKup1pY30tWBFdrFXLPSEQ7bT1b6wXG6vH5UfuRHMK1lWjG+6tcAJ6CGx 1YVnh3e/eG6R+iFWSj8zs3bkW+gVdhfNXU2G4Z2o/HBMxOUvuFy0xiMZ61uLQh73+pOy wR1/x1L9uZWdNw1dT7R0rVZDUBd1hs0xRtjHuBGkaxuUbXNijvldu5L+onRUevNMt82s KUwqHCd8AtyUyW7evWQ8dszOfTCj2RmQPuItYMzzRA8nJp4HSTnRxjus8CGdtSYIGNI9 nvmPDGByyfcA73EWGekqmNksGAJr6rGo/JUTq76yQmak0Zb0rBRmOFPpbCx9TB+hHoYi CAjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=C+xjOIJqle8fLMki8RkAlqZnMZCxGotyo7pIQ08QPiI=; b=JtbeK7nRh5d49D6RavmeXFXjmbwmi0EgN3TIc+8ERbevCEnQb7zlEDSC3VSN5pJai0 u51fOR2JX+5n8xHnZuQImbgz/KrthOgROGhVwFJdf3s7QUUs/LroHNqOQx7uR06a31JX JhjAZ2l0gqG47krYz7go0H9JCDGm007V2JbgdDnoO6mm4ZFf8SilxgJk5fy9xnE6PiAO lYmWv3V2reL/RXgsxVeOecAzQqBHJxQp4sBeO+FBcaKSYBcEu7iplqvMZdyo5ALbmAz6 GkmrzzydFTpSYaSrhqoEi+4HiNJR1rrfjy6Zg08X2qo4+BOxFIOmO6cou4SAL8fIt1Uw Co4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y23-v6si1638540pfb.284.2018.07.26.08.39.51; Thu, 26 Jul 2018 08:40:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731769AbeGZQ4X (ORCPT + 99 others); Thu, 26 Jul 2018 12:56:23 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:49937 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730298AbeGZQ4X (ORCPT ); Thu, 26 Jul 2018 12:56:23 -0400 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1fiiLy-0001Re-20; Thu, 26 Jul 2018 17:38:58 +0200 Date: Thu, 26 Jul 2018 17:38:58 +0200 From: Sebastian Andrzej Siewior To: Pintu Kumar Cc: Thomas Gleixner , linux-rt-users@vger.kernel.org, open list , linux-arm-kernel@lists.infradead.org Subject: Re: [PREEMPT_RT]: Using printk-rt-aware.patch in non-rt kernel Message-ID: <20180726153857.abxfebvxjcp4jqgx@linutronix.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-07-18 20:19:15 [+0530], Pintu Kumar wrote: > Hi All, Hi, > I have a question about PREEMPT_RT patch for 3.10 kernel. > I am trying to port this rt patch: 0224-printk-rt-aware.patch.patch > (see the patch below), in non-rt kernel. > I could able to successfully apply this patch after replacing: > migrate_enable/disable with preempt_enable/disable. > Things were working fine so far. Why? > Then, I noticed that "printk" from interrupt context is not appearing > on console (minicom), if console shell is active. > However, it appears on the dmesg output. > > So, I am wondering, what could be the cause of this patch for this > behavior in non-rt kernel? > Is this the expected behavior, even on PREEMPT_RT kernel? I *think* it is but there are hardly any prints from atomic context for anyone to notice. And the next print from non-atomic context should flush it out. > Is there a way we can fix this issue on non-rt kernel? I would guess that a wakeup to klogd would fix it. > Please help us with your suggestions. > > Thanks, > Pintu Sebastian