Received: by 10.192.165.156 with SMTP id m28csp811863imm; Thu, 19 Apr 2018 07:58:59 -0700 (PDT) X-Google-Smtp-Source: AIpwx49l6qH0o086uKmSh1XlPCA9V/LJPuuNEADmWed+Z6WYp1GGd9Qdhv/RS3y1PxB+wIUSOuIL X-Received: by 10.98.178.208 with SMTP id z77mr5978708pfl.122.1524149939224; Thu, 19 Apr 2018 07:58:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524149939; cv=none; d=google.com; s=arc-20160816; b=ugOdOffkXubZ3OyQoFzW7mXlw93Hzy29Df+Arebu90uyYQAmzfnXa6hG2UI3MRR46s i+6k0nDfeZ5RZ77/I96pgBWs9Vo7TBrB5BuHc/J/vBVZm/bZVkQ8vwo4SmN93quedoZL A3vV9Gf1CJiI7IYYio/wOq4JetTIkvLXXM2pUnXC/t8bzqzgowWjmCu0vI8NASbkZS8y rmP09WM8ncfrbWKepxDAz5o0gG7C/SJsuqmqf/QFnPIbfAouXKpBAZcG66w2hdfWdU6W VM2EikhtK2sIzJCNk1XvmnbLeiK1WGdvwRs99KBru6zGyaxJHkbVRBtYCJzoTM9EkJ9V dSfw== 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=1EAUrQ32NQrr2oOiohA5oMzHmKglMkQZL3LEDZlXgFo=; b=A6g5rKqeDICQgxirJ4rTydHXvuWWvPAEzEvMXs6qSEjUB6ta9F77toZj6/OwLV/q7w CSbU5+WW66gja9v09MtGzI0yO2gEqcuxtqdATqaGPhitjNTjB5h1bC+/RHJR3+BWjXzT fcb+GPk4QZGxcD5JhSn95BOAukoJBEe0qv+4wVoEau1fjEbJEa8ZiUYchszdj1j4Hn20 V94xlOn8adeu+bpC/ujwxl1l4iOD/msrveK+dQe9CFyWFof95JHcKGc3WJjPuBB3o7l4 r8p38FYP0gvXbxOL++JFlLEnC1/djkZDR62FBGHv5tdx1y8OjQYmN6YJjEZvIgY1Plsn 6HHw== 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 c41-v6si2328927plj.503.2018.04.19.07.58.45; Thu, 19 Apr 2018 07:58:59 -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 S1753517AbeDSO46 (ORCPT + 99 others); Thu, 19 Apr 2018 10:56:58 -0400 Received: from stargate.chelsio.com ([12.32.117.8]:43448 "EHLO stargate.chelsio.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753171AbeDSO44 (ORCPT ); Thu, 19 Apr 2018 10:56:56 -0400 Received: from localhost (scalar.blr.asicdesigners.com [10.193.185.94]) by stargate.chelsio.com (8.13.8/8.13.8) with ESMTP id w3JEuX7a005546; Thu, 19 Apr 2018 07:56:33 -0700 Date: Thu, 19 Apr 2018 20:26:06 +0530 From: Rahul Lakkireddy To: Greg KH 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" , Ganesh GR , Nirranjan Kirubaharan , Indranil Choudhury Subject: Re: [PATCH net-next v4 1/3] vmcore: add API to collect hardware dump in second kernel Message-ID: <20180419145605.GA30325@chelsio.com> References: <20180419082456.GA8617@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180419082456.GA8617@kroah.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, April 04/19/18, 2018 at 13:54:56 +0530, Greg KH wrote: > 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. > Ok. Will fix this. > > + 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? > The API is generic enough to collect any type of device's dump. Any driver that wants to collect its underlying hardware/firmware dump can use the API. In our case, cxgb4 driver collects dumps of the underlying Chelsio network devices. Thanks, Rahul