Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp5594807ybv; Tue, 11 Feb 2020 19:29:27 -0800 (PST) X-Google-Smtp-Source: APXvYqwg+JTQqnkC+ORs2pPy9kCyyCguiyAZ6iLkDxe/HiZnuj5kpH1ZVYmjwklVHWxLe9zjxQdr X-Received: by 2002:a9d:170a:: with SMTP id i10mr7645682ota.284.1581478167025; Tue, 11 Feb 2020 19:29:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581478167; cv=none; d=google.com; s=arc-20160816; b=W00ZY1RI+dMrpOnulL6kAzjeADFyLSv8SvMV8q0R7w5ssBeqWmQ27doEUEMBoJJ+5C sBXq2zTVSa/9fVh8/Raz3HnoC5kiR933LGS/eFvouhnFx/Qa5HcWmXKPA/h49hWzoqlQ PSJe7cETQ+NIsxR+PkFRUUzDgiY5Q6U0Da1Ar2z6MKJxiKl8jxaCjvs3Ytilau2RTSVj 79NcvWThfC3pkCI07C4ylh/x0vsSVjiKp6CM21hXdLfbNqaOZvd8wCLdPKjThals8rat fpbxP+QR6JtQIXp/oBAmEXxa/xzURNfgNykKVoCvwIVHhq0AUPq9w9cLhRQLEClNcOTF UtFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=TP9ch7LMzFdTjqPB3a7B6fRyzqxRv9PO3qS7oYYwL2w=; b=XDjaw0R+A47nOdcjmYdlgZKhW0t78ulTQeSCFN9Xe6cvoaYNU46F5cYfMsIubBgPaA VZCN2XNjS6RwRLuPTD7ykrPC925ZpV4CN6UQpbtuAbC3Efn2DOiSL3I0F3/IJ30g9Zxp MSIqMMMCUlHSp/5nZ+vtv1wNbkvpzG0gOeR3OVaQG6MZpQ1pAihMbdsyI3NnY8GBCejg /2so2d0SYamhKXXhZz7ApbnI6k9VIO72Wn4fL9OZeDBBcpsgOK3VcFlmb6flF47uL20c qsfr1E3JMQ7W5WloHoLpuVV3Oc/pThse1s5SrkzJBTJQEStdf7D5EMxgY25iJx5U4BvO UH3g== 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 m26si3195809otn.307.2020.02.11.19.29.15; Tue, 11 Feb 2020 19:29:27 -0800 (PST) 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 S1727883AbgBLD15 (ORCPT + 99 others); Tue, 11 Feb 2020 22:27:57 -0500 Received: from mail.kernel.org ([198.145.29.99]:37534 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727743AbgBLD15 (ORCPT ); Tue, 11 Feb 2020 22:27:57 -0500 Received: from rorschach.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4E1B32082F; Wed, 12 Feb 2020 03:27:56 +0000 (UTC) Date: Tue, 11 Feb 2020 22:27:54 -0500 From: Steven Rostedt To: Sergey Senozhatsky Cc: Petr Mladek , Peter Zijlstra , linux-kernel@vger.kernel.org, Sergey Senozhatsky , Andrew Morton , Dmitry Monakhov , Konstantin Khlebnikov Subject: Re: [PATCH] kernel/watchdog: flush all printk nmi buffers when hardlockup detected Message-ID: <20200211222754.0185b9b3@rorschach.local.home> In-Reply-To: <20200212030403.GC13208@google.com> References: <158132813726.1980.17382047082627699898.stgit@buzz> <20200212011551.GA13208@google.com> <20200211214958.5d8f4004@rorschach.local.home> <20200212030403.GC13208@google.com> X-Mailer: Claws Mail 3.17.4git76 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 12 Feb 2020 12:04:03 +0900 Sergey Senozhatsky wrote: > Oh, yes, ftrace printks a lot. But I sort of forgot why don't we do > the same for "regular" NMIs. So NMIs use per-cpu buffers, expect for > NMIs which involve ftrace dump. I'm missing something here. Well, ftrace_dump() is called from NMI context when the system is about to crash (ftrace_dump_on_oops). And at that moment, we care more about the trace than other output (it's most like to contain the information that caused the bug). But for things like sysrq-l, that does a printk in NMI context for normal operations, we don't want strange races to occur and affect other printk operations. Having them in buffers controls the output a bit better. But with the new printk ring buffer work, perhaps that's no longer necessary. -- Steve