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.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,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 9148CC4361B for ; Wed, 9 Dec 2020 11:15:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 468AB23433 for ; Wed, 9 Dec 2020 11:15:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730425AbgLILPo (ORCPT ); Wed, 9 Dec 2020 06:15:44 -0500 Received: from mx2.suse.de ([195.135.220.15]:35746 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730161AbgLILPo (ORCPT ); Wed, 9 Dec 2020 06:15:44 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1607512498; 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=0DasMEnu8hJ2pUKVJiARohcG8vDoST0haFmbQ/L0X3U=; b=mbEFLRPFub3li48UCaK7JXrE15G1HNVVnbOdGNTrHiSfD8+f/JJSFF6cuKDnTUJcmgJcoF sM0K+XevCU1t5w9nuBsYKaMbSxn/fB9E5v4kcnUedUH0ZJnZ7B9wEnxUG+aK6pjy///2wQ /tjPPSE+J1/E+Ot9qZPG2A3wo3gB864= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id DBA6AAD09; Wed, 9 Dec 2020 11:14:57 +0000 (UTC) Date: Wed, 9 Dec 2020 12:14:57 +0100 From: Petr Mladek To: John Ogness Cc: Sergey Senozhatsky , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Greg Kroah-Hartman , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [PATCH next v4 0/2] printk: remove logbuf_lock writer-protection of ringbuffer Message-ID: References: <20201209004453.17720-1-john.ogness@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201209004453.17720-1-john.ogness@linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 2020-12-09 01:50:51, John Ogness wrote: > 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. Both patches are pushed in printk/linux.git, branch printk-rework. I hurried so that we could get some testing linux-next before the merge window opens. We are going to see if the many barriers in the ring buffer code are enough ;-) I keep my fingers crossed. Best Regards, Petr