From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= Subject: Re: PCI passthrough of USB controllers on Xen 4.8.1, Linux 4.9.29, stubdomain Date: Tue, 6 Jun 2017 12:41:58 +0200 Message-ID: <20170606104158.GE1335@mail-itl> References: <20170602105719.GK10404@mail-itl> <593685CD020000780015FAAA@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7543251457051049935==" Return-path: In-Reply-To: <593685CD020000780015FAAA@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Jan Beulich Cc: HW42 , xen-devel List-Id: xen-devel@lists.xenproject.org --===============7543251457051049935== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="d03Wvsl4acTHE0IU" Content-Disposition: inline --d03Wvsl4acTHE0IU Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 06, 2017 at 02:37:01AM -0600, Jan Beulich wrote: > >>> On 02.06.17 at 12:57, wrote: > > And in this case, dom0 also prints: > >=20 > > [ 49.155606] pciback 0000:00:14.0: Driver tried to write to a=20 > > read-only configuration space field at offset 0x82, size 2. This may be= =20 > > harmless, but if you have problems with your device: > > 1) see permissive attribute in sysfs > > 2) report problems to the xen-devel mailing list alo= ng=20 > > with details of your device obtained from lspci. > > [ 66.247644] pciback 0000:00:14.0: cache line size of 64 is not= =20 > > supported > > [ 66.247646] xen_pciback: 0000:00:14.0: cannot enable=20 > > memory-write-invalidate (-22) > >=20 > > Enabling permissive mode doesn't change anything. >=20 > I doubt this - the first of the messages won't be logged in permissive > mode. Yes, of course. But the other lines and overall effect is the same. > We'll also need to know what register there is at address 0x82 > (possibly visible from a sufficiently verbose lspci in Dom0). >=20 > As to the latter two - lspci output may also help understand > what the issue with cache line size here is. A second source of > information may be lspci output for the device with its normal > driver loaded and attached in Dom0. Below is lspci of those two devices, in dom0, with normal driver attached. Would lspci from domU be useful too? [root@dom0 ~]# lspci -s 00:1d.0 -vvv 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Control= ler (rev 03) (prog-if 20 [EHCI]) Subsystem: Intel Corporation Device 7270 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Steppi= ng- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- SERR- TAbort- SERR-