xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
	qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Xen-devel] [PATCH RESEND] fix MSI injection on Xen
Date: Wed, 27 Jan 2016 12:41:38 -0500	[thread overview]
Message-ID: <20160127174138.GF2258@char.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1601131434120.13564@kaball.uk.xensource.com>

On Wed, Jan 13, 2016 at 02:59:09PM +0000, Stefano Stabellini wrote:
> On Xen MSIs can be remapped into pirqs, which are a type of event
> channels. It's mostly for the benefit of PCI passthrough devices, to
> avoid the overhead of interacting with the emulated lapic.
> 
> However remapping interrupts and MSIs is also supported for emulated
> devices, such as the e1000 and virtio-net.
> 
> When an interrupt or an MSI is remapped into a pirq, masking and
> unmasking is done by masking and unmasking the event channel. The
> masking bit on the PCI config space or MSI-X table should be ignored,
> but it isn't at the moment.
> 
> As a consequence emulated devices which use MSI or MSI-X, such as
> virtio-net, don't work properly (the guest doesn't receive any
> notifications). The mechanism was working properly when xen_apic was

By xen_apic I presume the Linux Xen APIC code?

> introduced, but I haven't narrowed down which commit in particular is
> causing the regression.

It sounds like the issue was due to the Xen APIC code? Or am I misreading it?

  reply	other threads:[~2016-01-27 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 14:59 [PATCH RESEND] fix MSI injection on Xen Stefano Stabellini
2016-01-27 17:41 ` Konrad Rzeszutek Wilk [this message]
2016-01-28 10:32   ` Stefano Stabellini
2016-02-04 17:05 ` Stefano Stabellini
2016-02-04 18:16   ` Michael S. Tsirkin
2016-02-08 11:18     ` Stefano Stabellini

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=20160127174138.GF2258@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xensource.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).