All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: [Xen-devel] Broken PCI device passthrough, after XSA-302 fix?
Date: Sat, 4 Jan 2020 02:07:59 +0100	[thread overview]
Message-ID: <20200104010759.GA2507@mail-itl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1618 bytes --]

Hi,

I have a multi-function PCI device, behind a PCI bridge, that normally
I assign to a single domain. But now it fails with:

(XEN) [VT-D]d14: 0000:04:00.0 owned by d0!<G><0>assign 0000:05:00.0 to dom14 failed (-22)

This is Xen 4.8.5 + XSA patches. It started happening after some update
during last few months, not really sure which one.

I guess it is because quarantine feature, so initial ownership of
0000:05:00.0 is different than the bridge it is connected to.
I'm not sure if relevant for this case, but I also set
pcidev->rdm_policy = LIBXL_RDM_RESERVE_POLICY_RELAXED.

Booting with iommu=no-quarantine helps. Note I do not use `xl
pci-assignable-add` command, only bind the device to the pciback driver
in dom0.

Relevant part of lspci and lspci -t:

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
..
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
..
04:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
05:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43)
05:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43)
05:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04)

-[0000:00]-+-00.0
..
           +-1c.3-[04-05]----00.0-[05]--+-00.0
           |                            +-00.1
           |                            \-00.2


-- 
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

             reply	other threads:[~2020-01-04  1:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04  1:07 Marek Marczykowski-Górecki [this message]
2020-01-06 11:18 ` [Xen-devel] Broken PCI device passthrough, after XSA-302 fix? Jan Beulich
2020-01-06 14:04   ` Marek Marczykowski-Górecki
2020-01-06 14:16     ` Marek Marczykowski-Górecki
2020-01-06 14:29       ` Marek Marczykowski-Górecki
2020-01-06 14:38     ` Jan Beulich
2020-01-06 16:37       ` Marek Marczykowski-Górecki
2020-01-06 13:06 ` Jan Beulich
2020-01-19 10:39   ` Pasi Kärkkäinen
2020-01-20  8:36     ` Jan Beulich
2020-01-20  9:10       ` Pasi Kärkkäinen

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=20200104010759.GA2507@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --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.