qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Wangting (Kathy)" <kathy.wangting@huawei.com>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Fwd: [question] About MSI for vioscsi
Date: Thu, 8 Jan 2015 17:27:25 +0800	[thread overview]
Message-ID: <54AE4D7D.5040407@huawei.com> (raw)
In-Reply-To: <1420707684.4185.3.camel@oscar>



On 2015-1-8 17:01, Vadim Rozenfeld wrote:
> 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.
> 
Where is the inf file? Do you mean qemupciserial.inf?
>>
>>    Thank you very much.
>>
>>    Best wishes,
>>
>>    Ting Wang
>>
>>
>>
>>
>>
>>
>>
>>
> 
> 
> 
> 

  reply	other threads:[~2015-01-08  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54AE4253.2090206@huawei.com>
2015-01-08  8:40 ` [Qemu-devel] Fwd: [question] About MSI for vioscsi Wangting (Kathy)
2015-01-08  9:01   ` Vadim Rozenfeld
2015-01-08  9:27     ` Wangting (Kathy) [this message]
2015-01-08 10:03       ` Vadim Rozenfeld
2015-01-09  3:48         ` Wangting (Kathy)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54AE4D7D.5040407@huawei.com \
    --to=kathy.wangting@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vrozenfe@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).