From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54366) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ynodj-0002UO-1G for qemu-devel@nongnu.org; Thu, 30 Apr 2015 09:36:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ynodd-0005Te-VI for qemu-devel@nongnu.org; Thu, 30 Apr 2015 09:36:30 -0400 Date: Thu, 30 Apr 2015 15:36:21 +0200 From: Kevin Wolf Message-ID: <20150430133621.GC25594@noname.redhat.com> References: <553A91AE.10708@wendan.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH] Enable NVMe start controller for Windows guest. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Keith Busch Cc: Daniel Stekloff , qemu-block@nongnu.org, qemu-devel@nongnu.org, stefanha@redhat.com [Cc: qemu-block] Am 24.04.2015 um 21:19 hat Keith Busch geschrieben: > On Fri, 24 Apr 2015, Daniel Stekloff wrote: > >Windows seems to send two separate calls to NVMe controller configuration. The > >first sends configuration info and the second the enable bit. I couldn't > >enable the Windows 8.1 in-box NVMe driver with base Qemu. I made the > >following change to store the configuration data and then handle enable and > >NVMe driver works on Windows 8.1. > > Hm, Microsoft's driver must be issuing MMIO reads to mask in the enable > bit rather than keep the state known. Sounds odd, but thanks for the fix. > > Acked-by: Keith Busch Thanks, applied to the block branch. Kevin