From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: Xen 4.3/AMD: setup ssss:bb:dd.f for d0 failed (-ENODEV) Date: Mon, 22 Jul 2013 14:55:15 +0200 Message-ID: <51ED2BB3.4050806@canonical.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3906409904213600472==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============3906409904213600472== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigC1F141E9C213C5CE0FB22119" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC1F141E9C213C5CE0FB22119 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable While testing Xen 4.3 on my AMD testbox I noticed the following output fr= om the hypervisor (this has no visible effect on at least simple operation): (XEN) setup 0000:00:18.0 for d0 failed (-19) (XEN) setup 0000:00:18.1 for d0 failed (-19) (XEN) setup 0000:00:18.2 for d0 failed (-19) (XEN) setup 0000:00:18.3 for d0 failed (-19) (XEN) setup 0000:00:18.4 for d0 failed (-19) (XEN) setup 0000:00:19.0 for d0 failed (-19) (XEN) setup 0000:00:19.1 for d0 failed (-19) (XEN) setup 0000:00:19.2 for d0 failed (-19) (XEN) setup 0000:00:19.3 for d0 failed (-19) (XEN) setup 0000:00:19.4 for d0 failed (-19) The PCI devices related to the output are all PCI host bridges: 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control This all seems to be related to PCI passthrough setup started from xen/drivers/passthrough/vtd/iommu.c:intel_iommu_dom0_init() or xen/drivers/passthrough/amd/pci_amd_iommu.c:amd_iommu_dom0_init() While the Intel code skips over bridge type entries, the AMD code has no = such exception and will fail the handler with -ENODEV when find_iommu_for_devi= ce fails. But I am not sure one can just compare implementations here. Would someone have more insight to decide whether skipping host bridges i= n amd_iommu_setup_dom0_device would make sense? I do not see any bad effect= s caused by this but it does not look good and did not happen before. -Stefan --------------enigC1F141E9C213C5CE0FB22119 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCgAGBQJR7SuzAAoJEOhnXe7L7s6jzHIQAK+SH5ZxPUZQoulNzIDoIA1i dfD7TUGJWGoW05XDQP36sFzevCHYmMQ9Syvj8OEPld9SSAYkX/JD5MAyyPx7qrjJ NgV/xd7S2CV/IHdWZXOIOF3zhsOuu1RxofxJ0Vm/toGSI4YXIO8TqlHksYQji0qr HUO3DsHZlUH48q43eYHKt/rYfTit7LII1XU954Z5wvz++hkjK4sYl7eaPB3WGUyj xYdE+N4L+UXdSoK0n1ZcJo4HYKPHo1twTJOIUANE/XV4II7pMpHvstAVxuYLOudG LQvA+OrAI5WM3DBpYlBag9eRt4dB18AYJ9xLVnUw8zXNNZfRBt6qx5IWSFvhx3px HGUDzdHTqk+mbcClpXLwX+XIQhchxbszgghJahZbsTRntJVFzGfrRa4ofi3OXjA/ XlTqsLfmWsIIR8x6NlhTVepQm4I9DXoL0FOOIvqhfHgVexeq76BBSH/NTrAv7Qm0 i+o1ShdmUq6/Vj8aDBU12ymz7xgynbZfIwoHJjxMNAHjVoEJffmm/co8yU+kpqLe 1YBoin0C3IifHr0lyz/UFzW1/7/7q3kdSkyq+XT4gr7KpJUX7w9YvlS9HBDgOKz8 zdyZZ7fFWP/ILda5JwHOvVT3QXubKukHyCdo1/qWCufTQO/xonu7Wqoo5Ga4EKcS jBPt/pHd+aR4HAjLoHhU =w2Nl -----END PGP SIGNATURE----- --------------enigC1F141E9C213C5CE0FB22119-- --===============3906409904213600472== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3906409904213600472==--