From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: "James McKenzie" <james.mckenzie@bromium.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
qemu-devel@nongnu.org, "Paul Durrant" <paul.durrant@citrix.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 5/6] xen-pt: Hide MSI-X from xen stubdoms
Date: Tue, 12 Mar 2019 15:29:55 +0100 [thread overview]
Message-ID: <20190312142955.GA1835@mail-itl> (raw)
In-Reply-To: <CAKf6xpvVBDGCmbcgU0u39Sh5NjFRf95O3UQ=_DmD6uVb-vx-sA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2516 bytes --]
On Tue, Mar 12, 2019 at 09:58:56AM -0400, Jason Andryuk wrote:
> On Tue, Mar 12, 2019 at 8:38 AM Marek Marczykowski-Górecki
> <marmarek@invisiblethingslab.com> wrote:
> >
> > On Tue, Mar 12, 2019 at 01:04:19PM +0100, Roger Pau Monné wrote:
> > > On Mon, Mar 11, 2019 at 02:02:15PM -0400, Jason Andryuk wrote:
> > > > MSI-X is not supported in Xen stubdoms, so it must be disabled. Use the
> > > > existing xen_pt_hide_dev_cap to hide when running under -xen-stubdom.
> > >
> > > I'm afraid this requires some more context. What's the actual issue
> > > that prevents MSI-X from working?
> >
> > At least missing "Fix PCI passthrough for HVM with stubdomain" series,
> > but that's mostly on Xen side (+ one change how QEMU enable MSI-X in
> > config space).
> > Some of it can be worked around by enabling permissive mode. Jason, did
> > you had a chance to test it with any MSI-X device?
> > I'm not aware of anything thing particular that breaks MSI-X but not
> > MSI. Besides much less devices lying around to test MSI-X...
>
> OpenXT and Qubes have used a compile time patch that disabled MSI-X
> for a long time. The OpenXT patch description doesn't help:
> """
> Currently we do not support MSI-X setup for PCI devices passed through.
>
> Although the specification mentions that PCI-e devices might implement only
> MSI-X there is not a lot of those and mostly none that we have encountered yet.
> Considering that, we force devices to use MSI by hiding the MSI-X capability.
> """
>
> To be honest, I didn't question the reasoning and just made the
> compile-time disabling into a runtime disabling.
>
> I tested with a NEC uPD720200 XHCI controller supporting MSI-X. There
> was an error related to setting up MSI-X when I failed to pass the
> "-xen-stubdom" flag. I can pull that log when I get back to the
> machine. With this patch, MSI-X was hidden in the guest, but dom0
> showed MSI-X present but unused.
>
> Marek, is "Use xc_physdev_msi_set_enable for enabling MSI..." the QEMU
> patch you are refer to? Do you think permissive mode would allow
> MSI-X to work without that patch? I could test that out.
Yes, this one. Permissive mode should work around it.
There is also another patch about IRQ permission, but I believe you
already have it in OpenXT.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-12 14:30 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 18:02 [PATCH 0/6] Xen stubdom support Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-11 18:02 ` [PATCH 1/6] xen: Introduce -xen-stubdom option Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-11 18:06 ` Paolo Bonzini
2019-03-11 18:06 ` [Qemu-devel] " Paolo Bonzini
2019-03-11 19:46 ` Jason Andryuk
2019-03-11 19:46 ` [Qemu-devel] " Jason Andryuk
2019-03-11 18:02 ` [PATCH 2/6] xen: Move xenstore initialization to common location Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-13 15:01 ` Paul Durrant
2019-03-13 18:11 ` Jason Andryuk
2019-03-14 14:00 ` Paul Durrant
2019-03-11 18:02 ` [PATCH 3/6] xen: Skip backend initialization for stubdom Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-13 15:04 ` Paul Durrant
2019-03-11 18:02 ` [PATCH 4/6] xen: Set HVM_PARAM_DM_DOMAIN for stubdom on older Xen Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-11 18:02 ` [PATCH 5/6] xen-pt: Hide MSI-X from xen stubdoms Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-12 12:04 ` Roger Pau Monné
2019-03-12 12:38 ` Marek Marczykowski-Górecki
2019-03-12 13:58 ` Jason Andryuk
2019-03-12 14:13 ` Roger Pau Monné
2019-03-12 15:15 ` Jason Andryuk
2019-03-13 2:15 ` Jason Andryuk
2019-03-12 14:29 ` Marek Marczykowski-Górecki [this message]
2019-03-11 18:02 ` [PATCH 6/6] xen-pt: Round pci regions sizes to XEN_PAGE_SIZE Jason Andryuk
2019-03-11 18:02 ` [Qemu-devel] " Jason Andryuk
2019-03-13 15:09 ` Paul Durrant
2019-03-14 18:15 ` Jason Andryuk
2019-03-14 19:22 ` Simon Gaiser
2019-03-14 19:37 ` Andrew Cooper
2019-03-15 9:12 ` Paul Durrant
2019-03-14 20:45 ` Simon Gaiser
2019-03-15 9:17 ` Paul Durrant
2019-03-15 16:28 ` Andrew Cooper
2019-03-20 17:28 ` Jason Andryuk
2019-03-22 3:09 ` Roger Pau Monné
2019-03-22 19:43 ` Jason Andryuk
2020-01-13 19:01 ` [Xen-devel] " Jason Andryuk
2020-01-13 19:01 ` Jason Andryuk
2020-01-14 10:04 ` Roger Pau Monné
2020-01-14 10:04 ` Roger Pau Monné
2020-01-14 14:41 ` Jason Andryuk
2020-01-14 14:41 ` Jason Andryuk
2020-01-14 18:04 ` Roger Pau Monné
2020-01-14 18:04 ` Roger Pau Monné
2020-01-15 8:33 ` Durrant, Paul
2020-01-15 8:33 ` Durrant, Paul
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=20190312142955.GA1835@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=anthony.perard@citrix.com \
--cc=james.mckenzie@bromium.com \
--cc=jandryuk@gmail.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.