From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51089) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y98yT-0004aI-En for qemu-devel@nongnu.org; Thu, 08 Jan 2015 04:01:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y98yO-0005ly-Fr for qemu-devel@nongnu.org; Thu, 08 Jan 2015 04:01:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47256) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y98yO-0005lk-8P for qemu-devel@nongnu.org; Thu, 08 Jan 2015 04:01:44 -0500 Message-ID: <1420707684.4185.3.camel@oscar> From: Vadim Rozenfeld Date: Thu, 08 Jan 2015 20:01:24 +1100 In-Reply-To: <54AE4295.7040109@huawei.com> References: <54AE4253.2090206@huawei.com> <54AE4295.7040109@huawei.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Fwd: [question] About MSI for vioscsi List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Wangting (Kathy)" Cc: qemu-devel On Thu, 2015-01-08 at 16:40 +0800, Wangting (Kathy) wrote: > 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? Did you enable MSISupported in inf file? Cheers, Vadim. > > Thank you very much. > > Best wishes, > > Ting Wang > > > > > > > >