From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754990AbeASAUe (ORCPT ); Thu, 18 Jan 2018 19:20:34 -0500 Received: from mail.kernel.org ([198.145.29.99]:41934 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750762AbeASAU1 (ORCPT ); Thu, 18 Jan 2018 19:20:27 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4664E21456 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Thu, 18 Jan 2018 19:20:23 -0500 From: Steven Rostedt To: Pavel Machek Cc: Petr Mladek , Sergey Senozhatsky , akpm@linux-foundation.org, linux-mm@kvack.org, Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Linus Torvalds , Jan Kara , Mathieu Desnoyers , Tetsuo Handa , rostedt@rostedt.homelinux.com, Byungchul Park , Sergey Senozhatsky , Tejun Heo , linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 1/2] printk: Add console owner and waiter logic to load balance console writes Message-ID: <20180118192023.1c29abbb@gandalf.local.home> In-Reply-To: <20180118220323.GC17196@amd> References: <20180110132418.7080-1-pmladek@suse.com> <20180110132418.7080-2-pmladek@suse.com> <20180112115454.17c03c8f@gandalf.local.home> <20180118220323.GC17196@amd> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Jan 2018 23:03:24 +0100 Pavel Machek wrote: > > To demonstrate the issue, this module has been shown to lock up a > > system with 4 CPUs and a slow console (like a serial console). It is > > also able to lock up a 8 CPU system with only a fast (VGA) console, by > > passing in "loops=100". The changes in this commit prevent this module > > from locking up the system. > > > > #include > > #include > > #include > > #include > > #include > > #include > > Programs in commit messages. Not preffered way to distribute code, I'd > say. What about putting it into kernel selftests directory or > something like that? It's not really a program, but a module. I could add a real module that can test this, and people can modprobe it if they want to make sure there's no regressions. I can send a patch. -- Steve