Received: by 10.192.165.156 with SMTP id m28csp436211imm; Thu, 19 Apr 2018 01:26:29 -0700 (PDT) X-Google-Smtp-Source: AIpwx49tMtBNk9l5/Z6bTSo5lyaLC+LhH+5teZcAY36QgVi1/FgmJGFZpCeHtEcwOn4aKQNde1mp X-Received: by 10.99.114.78 with SMTP id c14mr4206787pgn.199.1524126388960; Thu, 19 Apr 2018 01:26:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524126388; cv=none; d=google.com; s=arc-20160816; b=GQ9ujIo2v5xOrOxZy1kj15NqfPwvKAMqiLiSFnA0IZEsS7pYcVJhqwID8AbNwkaQe5 Af8BYCHP9xKgtWFRq3yegZWUmZlH9MfgEUwYmWSXY6EvM+VGU1wSb7I0Szg3xNZb9Y4r tUnr7ayajh4Yh2eVSQggpwCgpCNeyTVF9GNs2BzKOBkMiOyzRzNa2u+KgvCKrp1YOWRe zLNrZL2F/h6yvYXXBIKJZvwZcVTbwyUgy2k04uwikKhDxQtcCkPNedtUpO3Qtxmf6F2b TGTdOxTLnmnluHYGzmxgUyov4GaKHBNuZjdYCHWgqSIMetMi77l3Emlguz4v92ix/Ky/ /0AA== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=Jo+LjX7f7e+pRa9yDbJ7XJ2vEgMB6L/OseD0f0O3aYY=; b=vhM3aIuqxaDGAjN2yVzfFbal2VF1lU0ogNHUqajiydbf2gb+LfxDdMz2RE2jUQXrUi uM6jPr6oQJfbWR0A2stD+um331rd7EKUt/pJJbdqzWQ64FR3D3UM92NdLVNNmK1WtizR VF/f4xAMb8JapU2NiTqbUdAeRKLqx6wchoJVvl9WeW2+1dC+RIMWmZfjOUuwUlCorm9G a32Spbby7sdFJA4aUg7DTIpPaCXWzXDgMHibbWPAjsFA9t1N/WtP+y1PEuTxcGmzEpbP 0m4dIGAlL/lHTMNvQxEdrSZaK4vvi9jTW5bHAAWqGESh2Ekm4fXdJxvUjVdWytO9EJ52 z5lw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 14-v6si2908738ple.450.2018.04.19.01.26.13; Thu, 19 Apr 2018 01:26:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751151AbeDSIZF (ORCPT + 99 others); Thu, 19 Apr 2018 04:25:05 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:43870 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750799AbeDSIZD (ORCPT ); Thu, 19 Apr 2018 04:25:03 -0400 Received: from localhost (D57E6652.static.ziggozakelijk.nl [213.126.102.82]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id A368E34; Thu, 19 Apr 2018 08:25:02 +0000 (UTC) Date: Thu, 19 Apr 2018 10:24:56 +0200 From: Greg KH To: Rahul Lakkireddy Cc: netdev@vger.kernel.org, kexec@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, davem@davemloft.net, viro@zeniv.linux.org.uk, ebiederm@xmission.com, stephen@networkplumber.org, akpm@linux-foundation.org, torvalds@linux-foundation.org, ganeshgr@chelsio.com, nirranjan@chelsio.com, indranil@chelsio.com Subject: Re: [PATCH net-next v4 1/3] vmcore: add API to collect hardware dump in second kernel Message-ID: <20180419082456.GA8617@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2018 at 01:14:17PM +0530, Rahul Lakkireddy wrote: > +config PROC_VMCORE_DEVICE_DUMP > + bool "Device Hardware/Firmware Log Collection" > + depends on PROC_VMCORE > + default y Only things that require the machine to keep working should be 'default y', please remove this, it's an option. > + help > + Device drivers can collect the device specific snapshot of > + their hardware or firmware before they are initialized in > + crash recovery kernel. If you say Y here, the device dumps > + will be added as ELF notes to /proc/vmcore Which exact "device drivers" are you referring to here? thanks, greg k-h