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 X-Spam-Level: X-Spam-Status: No, score=-10.2 required=3.0 tests=BAYES_00, BUG6152_INVALID_DATE_TZ_ABSURD,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,INVALID_DATE_TZ_ABSURD, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C565DC4361B for ; Wed, 9 Dec 2020 00:45:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9716323AA8 for ; Wed, 9 Dec 2020 00:45:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730004AbgLIApg (ORCPT ); Tue, 8 Dec 2020 19:45:36 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:42372 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725940AbgLIApg (ORCPT ); Tue, 8 Dec 2020 19:45:36 -0500 From: John Ogness DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1607474693; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=ae9uzxlxHpW5A/C82t4ibLw8BtYB7x7/rGLRuHPYU60=; b=oP1C51DBdC+gY7X9SubEpdM7I+lgKs52bQDUaK8JXi+O6DqeVn4dpXG5ZiWOcH/Eforo28 RcqhBmE6FKtnSUFSGuQNyj8OjPPxwBYS9RtgnOIseqiAL+qjN1KGq4ihAB85b9myyy0s2i bZnU/Ti0ot6jNAhsxxEiqdX9CjL9bb2LN1XcOULGvQHMMLYcE7E0FF4WPn0n1wqSF1rI2f Ewy83uGV36XVCKHJZQI3FUTcFMVh+uQy2DCtSIzHbm6GfaX1HIqUVh9oLSDDaXYksHuN1i uGwgGTJ9aGbj8wSxyMVq/Z3a5WEj8YiZEFyEu38nSwJLQchfyFGthX37eMviiw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1607474693; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=ae9uzxlxHpW5A/C82t4ibLw8BtYB7x7/rGLRuHPYU60=; b=VsRjxxGEnhZN9QKRcMsKkdQP2D8sjJuQRwDGRM9n5H2dr6K0a+8QO3WNgRayG5vPNHPm0P NWBcFNb1PNZNYOAQ== To: Petr Mladek Cc: Sergey Senozhatsky , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Greg Kroah-Hartman , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: [PATCH next v4 0/2] printk: remove logbuf_lock writer-protection of ringbuffer Date: Wed, 9 Dec 2020 01:50:51 +0106 Message-Id: <20201209004453.17720-1-john.ogness@linutronix.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Here is a v4 of the series to partially remove logbuf_lock. v3 is here[0]. This series removes logbuf_lock usage of most ringbuffer writers. The remaining logbuf_lock users are using the lock to synchronize other variables. These other users will be addressed in a later series. I have tried to keep these changes minimal so that we can feel comfortable for the upcoming 5.11 merge window. Although small, this series is significant because it allows printk callers direct lockless access to the ringbuffer and it replaces the use of a static sprint buffer with sprint'ing directly to the reserved ringbuffer data block. This series is based on next-20201208. John Ogness [0] https://lkml.kernel.org/r/20201207222020.2923-1-john.ogness@linutronix.de John Ogness (2): printk: inline log_output(),log_store() in vprintk_store() printk: remove logbuf_lock writer-protection of ringbuffer kernel/printk/printk.c | 247 ++++++++++++++++++++++++----------------- 1 file changed, 147 insertions(+), 100 deletions(-) -- 2.20.1