From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D14E0C43334 for ; Mon, 11 Jul 2022 08:32:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230120AbiGKIcT (ORCPT ); Mon, 11 Jul 2022 04:32:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38854 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230103AbiGKIcQ (ORCPT ); Mon, 11 Jul 2022 04:32:16 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2F211F2DA for ; Mon, 11 Jul 2022 01:32:14 -0700 (PDT) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id ADE4C227A0; Mon, 11 Jul 2022 08:32:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1657528333; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=YoBpN1lvaI78X/r2NUb3VKRDnI51NNOYRbZMd29y4RQ=; b=fuhsIEI3JBw5P6zU6Qz0+dis0c9M02cRQJpY64Z+7xlikuJkEzDebQvC2UAiclEdXpVFDX PQ+uCwaw13j6UPDFbU3yMHkJZpE5gmquCJ7Tnn5ITca0FL0zthyLOu8M7oY3UHsU764+ju smrA7K4kfi165Q8p4eFgvZNquUBGoCc= Received: from suse.cz (unknown [10.100.208.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 625A42C171; Mon, 11 Jul 2022 08:32:13 +0000 (UTC) Date: Mon, 11 Jul 2022 10:32:13 +0200 From: Petr Mladek To: John Ogness Cc: Chris Down , linux-kernel@vger.kernel.org, Greg Kroah-Hartman , Sergey Senozhatsky , Steven Rostedt , Geert Uytterhoeven , kernel-team@fb.com Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each console to have its own loglevel Message-ID: References: <87o7xz5su4.fsf@jogness.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87o7xz5su4.fsf@jogness.linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 2022-07-08 21:10:35, John Ogness wrote: > On 2022-07-08, Petr Mladek wrote: > > The console-specific loglevel might be set by: > > > > + "console=device,options/loglevel" kernel parameter at boot time > > I ask if we avoid the use of "/loglevel" and instead use a generic > scheme of: > > console=device,option,option,option > > Of course, it would mean that the type of option would need to be > specified. Something like: > > console=ttyS0,115200n8,loglevel=3 I like this. It is longer but it makes the meaning very obvious. I just think about using ':' instead of '=' to distinguish the assignment of outer 'console' vs the inner 'loglevel' parameters. It seems to be used in some cases, for example, for ca_keys, crashkernel, drm.edid_firmware, efi_fake_mem. Even earlyprintk uses it for bus:device.function. > The reason why I make such a request is because I would like to be able > to support disabling threading for certain consoles. Something like: > > console=ttyS0,115200n8,nothread > > or when we have atomic consoles that we can specify that they are always > used with a "sync" option: > > console=ttyS0,115200n8,sync Good point. Best Regards, Petr