All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
	xen-devel <xen-devel@lists.xen.org>, Joe Jin <joe.jin@oracle.com>,
	stefano.stabellini@eu.citrix.com
Subject: Re: passthroughed msix device
Date: Wed, 27 Feb 2013 13:49:58 +0800	[thread overview]
Message-ID: <512D9E86.1080907@oracle.com> (raw)
In-Reply-To: <512C979E02000078000C105F@nat28.tlf.novell.com>


On 2013-02-26 18:08, Jan Beulich wrote:
>>>> On 26.02.13 at 09:56, DuanZhenzhong <zhenzhong.duan@oracle.com> wrote:
>> pci_msix_writel: Can't update entry 0 since MSI-X is already enabled
>> (fee00000 -> fee02000)
>> pci_msix_writel: Can't update entry 0 since MSI-X is already enabled
>> (00004059 -> 00004071)
> If you look at the code issuing this message, the situation is
> pretty clear (and I think it as described already in the past,
> albeit I have no link at hand): qemu lacks proper emulation of
> the mask bit. pci_msix_write() looks at the physical one, yet
> when the guest sets the virtual mask bit, nothing is being
> done at all to make the hypervisor also mask the physical
> entry:
>
>      if (offset == PCI_MSIX_ENTRY_VECTOR_CTRL) {
>          if (msix->enabled && !(val & PCI_MSIX_ENTRY_CTRL_MASKBIT)) {
>              xen_pt_msix_update_one(s, entry_nr);
>          }
>      }
>
> There's probably quite a bit of code to be written to make this
> work.
Is there plan of fixing it?

thanks
zduan

  reply	other threads:[~2013-02-27  5:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  8:56 passthroughed msix device DuanZhenzhong
2013-02-26 10:08 ` Jan Beulich
2013-02-27  5:49   ` Zhenzhong Duan [this message]
2013-02-27  8:36     ` Jan Beulich
2013-02-28  4:57       ` Zhenzhong Duan

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=512D9E86.1080907@oracle.com \
    --to=zhenzhong.duan@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=joe.jin@oracle.com \
    --cc=konrad@kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.