Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5340756yba; Mon, 13 May 2019 09:13:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqy9ZX4O3qRWzNAyW0HdxV4MlWou6D3CsEA+c7ctRk1TfWi8Tz7V0LWqhi2ldkh2ktDGpKqY X-Received: by 2002:a62:7793:: with SMTP id s141mr34496590pfc.21.1557764006563; Mon, 13 May 2019 09:13:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557764006; cv=none; d=google.com; s=arc-20160816; b=U3GGLnS8tVaeoo3Q6BqdllQnzlH37fbHrjMBzfMIl/62tarVf6pvM+L+jSCChIcvKT WIPHGXu/azvhl9aWoh/rh4EAjXpqByRyN0f0psmdMHttjnm8OfDghKIMrisJdKQE3ncm NonXRBjL0Jje4ERNHkndRzeOjlbZq7X5rFN1EF4/7Pf+EDGBnyyHGRiECdslihiO7U02 4+ocjRE3uHB/BUgl3iu6jP+u1I9koevRQKOsH6G4rUnkL0Bo49eWq4h+DaQNAocwKH6L tFZXISUut7+XjUu2YZ1mlLJs+RTuITRQXvP7/coPmsRZtruaigfxqo26F7Cjo7V0DVuE anOQ== 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; bh=nStcWoIoK632i/Aw0r2x4ZkjyHD+fUrKHsO5J0J8GN8=; b=aMvPhJMcLlse1Rb2uiabXfF7kI7fKpBhbYlsWIrA1a3azMrBQJuVg19eCLLT9KLWuz eNq48InnT4dJlUJ2Xfb7Ks/eY9EfPGeZuDrDAV4jwnRqjHQsFJsYq5PjYITK9WVnYR3J jwIw/hodOvaMgacKKBf4xOoEX2+iVmkX2My0c+uSD4CV8H3m/6I+svciNljqbWlLc8P0 39xYJPRLcR0KgXLvIdF+e41DstcLq/Wmk+gZ6phd27wpAKDqFxJAUMuCyYBSoj6Yxhq3 w+bbLxVMOsSeXEDyITl7gCtsz+Y52EOcQ/UQL4/Uqx1r8Cqo/CgvFQmahraae7bLAGdb c2Qg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d137si18388682pga.23.2019.05.13.09.13.10; Mon, 13 May 2019 09:13:26 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730021AbfEMOnS (ORCPT + 99 others); Mon, 13 May 2019 10:43:18 -0400 Received: from mga06.intel.com ([134.134.136.31]:2011 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728970AbfEMOnR (ORCPT ); Mon, 13 May 2019 10:43:17 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 May 2019 07:43:17 -0700 X-ExtLoop1: 1 Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by FMSMGA003.fm.intel.com with ESMTP; 13 May 2019 07:43:16 -0700 Date: Mon, 13 May 2019 08:37:54 -0600 From: Keith Busch To: Mario.Limonciello@dell.com Cc: keith.busch@intel.com, hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org, rafael@kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, kai.heng.feng@canonical.com Subject: Re: [PATCH] nvme/pci: Use host managed power state for suspend Message-ID: <20190513143754.GE15318@localhost.localdomain> References: <20190510212937.11661-1-keith.busch@intel.com> <0080aaff18e5445dabca509d4113eca8@AUSX13MPC105.AMER.DELL.COM> <955722d8fc16425dbba0698c4806f8fd@AUSX13MPC105.AMER.DELL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <955722d8fc16425dbba0698c4806f8fd@AUSX13MPC105.AMER.DELL.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 Mon, May 13, 2019 at 02:24:41PM +0000, Mario.Limonciello@dell.com wrote: > This was not a disk with HMB, but with regard to the HMB I believe it needs to be > removed during s0ix so that there isn't any mistake that SSD thinks it can access HMB > memory in s0ix. Is that really the case, though? Where may I find that DMA is not allowed in this state? I just want an authoritative reference to attach to the behavior.