Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp806130ybk; Wed, 13 May 2020 13:39:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwWlB9YTcvS2YBLapVC1SoPocffPioM7NH49mX0TGQApWAOIyPAVKXzs+Icz2wo3T9PCXqv X-Received: by 2002:a05:6402:c2:: with SMTP id i2mr1395529edu.224.1589402391537; Wed, 13 May 2020 13:39:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589402391; cv=none; d=google.com; s=arc-20160816; b=O7PUQXyZ/FoO5QFwppJyP8qKIjH73BXT/VWxYBaJeMTrB+ZwcayYAryJVgeYLp8SYQ 18Fzw3i9TmBO9LlS8TpgjkNsmpLZK44JRx5czhwDIQ1YbuRxhfXyZnf05Lk9hDVLDM7H 5pHIq/+jG0ojYhDtYaDR3TSEYXE+UXVLW8BYTMeb/4kjet8b3am4z57KErFDB8hMaFsc lsQVQLzI2IFln4xayJey0Fq+QWBEY+8TcsjQB0eKmrVZ5bVoAvcsMskwgxlTEAGcw7iX u/vA/4M0+VEDmFAl2YjBBUpQkWbDtC0XCA/mfGKzCH2XZ+MjveG5QhNU0RyBUZ8mn49p GIMA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=rTvNfxEcdBjM7+rUnpuyw83WRb+cCXiZfeWKdT61OtU=; b=uWeld9/HXGkSdU0G69L147ms6k/y8qABJQ+TGcU5c0u5JjReVlDUEE7xywFmVIcydk T374Tzlnfm7f5uLkcqBbIH9e8azNH+GB1EWOdSluHR8XjxmhZKV/Vqm2MXikhwsI2Dki 0XunwaNzj+eWpdacDjETJYxEMI0MWuW+Vfo+5y8s0WYQ4Y/uZhDPWZtijdlhzeO5/DBj ugjnVzNVqbVdB96vvrp1k+I4V0kCFwOF4qmuS6W0SE+JU5VhNVBfw54UW2B7ShsZxWm0 t5npj0o4IjDEQSPrjydnx0S5bY0KYZ5UqXjsDujN9+W1H3bW4unPrPSIZsyiKgT/PaVI cUeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jIKglLNn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g20si581672ejc.29.2020.05.13.13.39.29; Wed, 13 May 2020 13:39:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jIKglLNn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731585AbgEMMFH (ORCPT + 99 others); Wed, 13 May 2020 08:05:07 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:25210 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728165AbgEMMFG (ORCPT ); Wed, 13 May 2020 08:05:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589371505; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rTvNfxEcdBjM7+rUnpuyw83WRb+cCXiZfeWKdT61OtU=; b=jIKglLNnAY7dYXnkEMtQevHfd6EjBKJPbIYvYNaDTaWQ3Q7hjPcgfC1sWRGyfvEWgdSIjV T/31wDTZigE/KOlA6eb2KFG1ZGehLqCoyarKN+njKSnSQ/is3Qrd02HEDfo5keHCWXSJVi XgzLynsKG4mXMSRg24yDGqXeePZP+Xg= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-249-PV_CE75mORq-Nt6Zud0-dw-1; Wed, 13 May 2020 08:05:03 -0400 X-MC-Unique: PV_CE75mORq-Nt6Zud0-dw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8666B1009447; Wed, 13 May 2020 12:05:01 +0000 (UTC) Received: from prarit.bos.redhat.com (prarit-guest.7a2m.lab.eng.bos.redhat.com [10.16.222.26]) by smtp.corp.redhat.com (Postfix) with ESMTP id 80CEC619C3; Wed, 13 May 2020 12:05:00 +0000 (UTC) Subject: Re: [PATCH v2 0/3] printk: replace ringbuffer To: John Ogness , Petr Mladek Cc: Peter Zijlstra , Sergey Senozhatsky , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Greg Kroah-Hartman , Andrea Parri , Thomas Gleixner , kexec@lists.infradead.org, linux-kernel@vger.kernel.org References: <20200501094010.17694-1-john.ogness@linutronix.de> From: Prarit Bhargava Message-ID: <8981615b-314a-1e55-1635-d17e3cbc544e@redhat.com> Date: Wed, 13 May 2020 08:05:00 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20200501094010.17694-1-john.ogness@linutronix.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/1/20 5:40 AM, John Ogness wrote: > Hello, > > Here is a v2 for the first series to rework the printk subsystem. The > v1 and history are here [0]. This first series only replaces the > existing ringbuffer implementation. No locking is removed. No > semantics/behavior of printk are changed. > > The VMCOREINFO is updated. RFC patches for the external tools > crash(8) [1] and makedumpfile(8) [2] have been submitted that allow > the new ringbuffer to be correctly read. > > This series is in line with the agreements [3] made at the meeting > during LPC2019 in Lisbon, with 1 exception: support for dictionaries > will not be discontinued [4]. Dictionaries are stored in a separate > buffer so that they cannot interfere with the human-readable buffer. > Hey John, I tested this on two 128-cpu ppc64le power8 boxes, and a 64 core x86_64 box using your prb-test testsuite with the latest upstream kernel. The tests ran successfully for ~16 hours without any problems. P.