Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1479455ybt; Thu, 2 Jul 2020 06:36:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzyR56YUVW6YOR5gux/tOmsbPZ555H6lnFDw4liY4z2cco4h0NUPhDXqr7MSdJNCTyY6piQ X-Received: by 2002:a50:d302:: with SMTP id g2mr35247806edh.312.1593696971013; Thu, 02 Jul 2020 06:36:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593696971; cv=none; d=google.com; s=arc-20160816; b=jhlLg2FyCWk6CzRjwGSMOCVhZSDdVltOTJk4jQZqN7F6inpfZIZduz/XLuQVav76AW 3Anz7yjYa46p5ysdsDMrEIVN44lnonKXwkDnJzH0Hg4McQiKU56vFS5Nen+uWM1nwC7s /XxxEbwLh2NpO1giFBvtSydFnmI+5SsQatVDhECZjqU9iKvlpZvDYa6cjZ5EY6e98dPB qxc8AeSTrBz9ETmCJLIci9MtUGRKEsXS702W3KGfUbpBaxEaGY0J21liEymr14Bn2+97 /c+savUHbjenXlhzGSOYeghoBDpZk/7f19cw5IhcYNlIyEl5XLT1gX66flN844zqbDj6 cigw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=9ZU+XBIepQBKYOa19yCU5G4dxwQk1ngiXU7latm4OOw=; b=JbxohTs/EH9prk7cyaONRy6IKPdHbfqwOPKRPHMDMDZwCslnaJzsDBtwKlGOyE7PiI ucKppm9CJWHUilymiqlolgZ9we3+nKySFF8BHDDf9lyIMOErwc6Z8gkie3XfLSElnp6W wlNlq873FQlGtNTxl1/5QVPTIuEAqtlpKdngm1EuiI9kUhFR2nMr0egZriU0OGWxjxFo DvIttTYSaooyfRj/ISi04rnU7M6Rfz2HHzOU71Z80xBrn37f/t9jOs81yStchTH00Gzv /tvHbJyvwFjaS3I6Pgjno0Q9Tj/c4yIyXqeRP7N8h1BFT/b5Y/C2kyXPsW6oRzykrSN6 9ORQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a41si7215668edf.30.2020.07.02.06.35.48; Thu, 02 Jul 2020 06:36:11 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729337AbgGBNcf (ORCPT + 99 others); Thu, 2 Jul 2020 09:32:35 -0400 Received: from mx2.suse.de ([195.135.220.15]:37896 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729119AbgGBNcf (ORCPT ); Thu, 2 Jul 2020 09:32:35 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id F0F89BC6C; Thu, 2 Jul 2020 13:32:33 +0000 (UTC) Date: Thu, 2 Jul 2020 15:31:10 +0200 From: Petr Mladek To: lijiang Cc: John Ogness , Peter Zijlstra , Sergey Senozhatsky , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Greg Kroah-Hartman , Andrea Parri , Thomas Gleixner , Paul McKenney , kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 3/3] printk: use the lockless ringbuffer Message-ID: <20200702133110.GE14288@alley> References: <20200618144919.9806-1-john.ogness@linutronix.de> <20200618144919.9806-4-john.ogness@linutronix.de> <87zh8imgs5.fsf@jogness.linutronix.de> <585a6a1b-931c-1034-e2cc-da2c4381751e@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <585a6a1b-931c-1034-e2cc-da2c4381751e@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2020-07-02 17:43:22, lijiang wrote: > 在 2020年07月02日 17:02, John Ogness 写道: > > On 2020-07-02, lijiang wrote: > >> About the VMCOREINFO part, I made some tests based on the kernel patch > >> v3, the makedumpfile and crash-utility can work as expected with your > >> patch(userspace patch), but, unfortunately, the vmcore-dmesg(kexec-tools) > >> can't correctly read the printk ring buffer information, and get the > >> following error: > >> > >> "Missing the log_buf symbol" > >> > >> The kexec-tools(vmcore-dmesg) should also have a similar patch, just like > >> in the makedumpfile and crash-utility. > > > > Yes, a patch for this is needed (as well as for any other related > > software floating around the internet). > > > > I have no RFC patches for vmcore-dmesg. Looking at the code, I think it > > would be quite straight forward to port the makedumpfile patch. I will > > Yes, it should be a similar patch. > > > try to make some time for this. > > > That would be nice. Thank you, John Ogness. > > > I do not want to patch any other software for this. I think with 3 > > examples (crash, makedumpfile, vmcore-dmesg), others should be able to > > It's good enough to have the patch for the makedumpfile, crash and vmcore-dmesg, > which can ensure the kdump(userspace) work well. I agree that this three are the most important ones and should be enough. Thanks a lot for working on it and testing it. Best Regards, Petr