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 4ABEDC04AA7 for ; Mon, 13 May 2019 14:43:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1BE672084A for ; Mon, 13 May 2019 14:43:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557758599; bh=nStcWoIoK632i/Aw0r2x4ZkjyHD+fUrKHsO5J0J8GN8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Ss0c/yeEMpMdyigsTz3pHNZ+m1Q8EJftlKyc5/WbwS8oWYhAiEO7GkXeu9QGXxVtf p30+XMZ2a4/sEywRj5TUmkC6zoo19i9UcjprRClOOuiBZ4rpMNk2Ri9GNAoEiXCRlL k/wF3u47kfzCECJAlmrsV0RdOXu6PuxZ2fBsT3oU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729976AbfEMOnS (ORCPT ); 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.