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=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT 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 0A78BC04AA7 for ; Mon, 13 May 2019 13:55:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BCA53208CA for ; Mon, 13 May 2019 13:55:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557755755; bh=pc2hyrvgvFiNrRyXcIWzUpLxl+BkeH6EsdHgGPqBv70=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=DUiP1JV02BA7aPNhGnB4JmapqLsxV1hYWpSJmhwd9BFCa55VS667stSSQlWw6Z00w RzQnMUr+1htWyhpZYL8JSx4K9iE834T/bAHYXiI6yqcVAg5gFutRNz/0KsL2ZTmCj/ nRf7DWZzOOKQUwHbibjbEHLmAKt2czYGPfdcCKVc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730002AbfEMNzy (ORCPT ); Mon, 13 May 2019 09:55:54 -0400 Received: from mga02.intel.com ([134.134.136.20]:32384 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729710AbfEMNzy (ORCPT ); Mon, 13 May 2019 09:55:54 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 May 2019 06:55:53 -0700 X-ExtLoop1: 1 Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga004.jf.intel.com with ESMTP; 13 May 2019 06:55:53 -0700 Date: Mon, 13 May 2019 07:50:31 -0600 From: Keith Busch To: Akinobu Mita Cc: "linux-nvme@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Johannes Berg , "Busch, Keith" , Jens Axboe , Christoph Hellwig , Sagi Grimberg , Minwoo Im , "Heitke, Kenneth" Subject: Re: [PATCH v3 5/7] nvme-pci: add device coredump infrastructure Message-ID: <20190513135031.GC15318@localhost.localdomain> References: <1557676457-4195-1-git-send-email-akinobu.mita@gmail.com> <1557676457-4195-6-git-send-email-akinobu.mita@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1557676457-4195-6-git-send-email-akinobu.mita@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, May 12, 2019 at 08:54:15AM -0700, Akinobu Mita wrote: > +static void nvme_coredump_logs(struct nvme_dev *dev) > +{ > + struct dev_coredumpm_bulk_data *bulk_data; > + > + if (!dev->dumps) > + return; > + > + bulk_data = nvme_coredump_alloc(dev, 1); > + if (!bulk_data) > + return; > + > + if (nvme_coredump_telemetry_log(bulk_data, &dev->ctrl)) > + dev->num_dumps--; > +} You'll need this function to return the same 'int' value from nvme_coredump_telemetry_log. A negative value here means that the device didn't produce a response, and that's important to check from the reset work since you'll need to abort the reset if that happens.