From: Simon Martin <furryfuttock@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Problems accessing passthrough PCI device
Date: Tue, 18 Nov 2014 13:24:05 -0300 [thread overview]
Message-ID: <19872515.20141118132405@gmail.com> (raw)
In-Reply-To: <5465CB080200007800047845@mail.emea.novell.com>
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
next prev parent reply other threads:[~2014-11-18 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 13:29 Problems accessing passthrough PCI device Simon Martin
2014-11-13 14:08 ` Jan Beulich
2014-11-13 15:07 ` Simon Martin
2014-11-13 15:52 ` Jan Beulich
2014-11-13 17:49 ` Simon Martin
2014-11-13 19:03 ` Konrad Rzeszutek Wilk
2014-11-13 19:21 ` Simon Martin
2014-11-13 19:29 ` Konrad Rzeszutek Wilk
2014-11-18 16:25 ` Simon Martin
2014-11-14 8:27 ` Jan Beulich
2014-11-18 16:24 ` Simon Martin [this message]
2014-11-18 16:49 ` Jan Beulich
2014-11-19 15:12 ` Simon Martin
2014-11-19 20:53 ` Konrad Rzeszutek Wilk
2014-11-21 16:53 ` Simon Martin
2014-11-21 17:26 ` Konrad Rzeszutek Wilk
2014-11-20 8:51 ` Jan Beulich
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=19872515.20141118132405@gmail.com \
--to=furryfuttock@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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.