From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y98fe-0005LI-2W for qemu-devel@nongnu.org; Thu, 08 Jan 2015 03:42:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y98fa-0007i9-JK for qemu-devel@nongnu.org; Thu, 08 Jan 2015 03:42:22 -0500 Received: from szxga01-in.huawei.com ([119.145.14.64]:32712) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y98fa-0007gC-4T for qemu-devel@nongnu.org; Thu, 08 Jan 2015 03:42:18 -0500 Message-ID: <54AE4295.7040109@huawei.com> Date: Thu, 8 Jan 2015 16:40:53 +0800 From: "Wangting (Kathy)" MIME-Version: 1.0 References: <54AE4253.2090206@huawei.com> In-Reply-To: <54AE4253.2090206@huawei.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Fwd: [question] About MSI for vioscsi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vadim Rozenfeld Cc: qemu-devel Hi Vadim, In order to enable MSI for vioscsi in virtio-win-0.1-74, I try to merge the patch about Bug 1077566 into it, but I find that MSI still doesn't work, because the value of IRQ is not negative in the device manager. I try to trace the I/O path with ENABLE_COM_DEBUG, and I find that pMsixCapOffset->MessageControl.MSIXEnable is zero when StorPortGetBusData returned in VioScsiFindAdapter, so MSI can't be enabled. I have tested that MSI is successfully enabled in virtio-win-0.1-81. But I still want to find out why the patch is not work in virtio-win-0.1-74. Is there some important points I missed? Thank you very much. Best wishes, Ting Wang