From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Martin Subject: Re: Problems accessing passthrough PCI device Date: Tue, 18 Nov 2014 13:24:05 -0300 Message-ID: <19872515.20141118132405@gmail.com> References: <198478230.20141113102921@gmail.com> <5464C971020000780004739B@mail.emea.novell.com> <196307380.20141113120732@gmail.com> <5464E1D9020000780004746B@mail.emea.novell.com> <429773295.20141113144907@gmail.com> <5465CB080200007800047845@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5465CB080200007800047845@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hello Jan, Friday, November 14, 2014, 5:27:36 AM, you wrote: >>> I implied your earlier statement to mean that. But - did you also >>> verify that the three flags actually end up set (ideally from both >>> DomU and Dom0 perspective)? The PCI backend may be screwing >>> up things... >> >> Yes I do verify the write. How do I check this from Dom0? > Just use lspci. I've just checked this with lspci. I see that the IO is being enabled. Any other idea on why I might be reading back 0xff for all PCI memory area reads? The lspci output follows. Before starting DomU smartin@smartin-xen:~$ lspci -s 00:19.0 -x 00:19.0 Ethernet controller: Intel Corporation Device 1559 (rev 04) 00: 86 80 59 15 00 00 10 00 04 00 00 02 00 00 00 00 After DomU initialisation smartin@smartin-xen:~$ lspci -s 00:19.0 -x 00:19.0 Ethernet controller: Intel Corporation Device 1559 (rev 04) 00: 86 80 59 15 02 00 10 00 04 00 00 02 00 00 00 00 After stopping DomU smartin@smartin-xen:~$ lspci -s 00:19.0 -x 00:19.0 Ethernet controller: Intel Corporation Device 1559 (rev 04) 00: 86 80 59 15 00 00 10 00 04 00 00 02 00 00 00 00 -- Best regards, Simon mailto:furryfuttock@gmail.com