On 19.11.14 at 16:12, furryfutt...@gmail.com wrote:
This is getting more interesting. It seems that something is
overwriting the pci-back configuration data.
Starting from a fresh reboot I checked the Dom0 pci configuration and
got this:
root@smartin-xen:~# lspci -s 00:19.0 -x
Hello Jan and Konrad,
Tuesday, November 18, 2014, 1:49:13 PM, you wrote:
I've just checked this with lspci. I see that the IO is being enabled.
Memory you mean.
Yes. Sorry.
Any other idea on why I might be reading back 0xff for all PCI
memory area reads? The lspci output follows.
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
Hello Konrad,
Thursday, November 13, 2014, 4:29:15 PM, you wrote:
On Thu, Nov 13, 2014 at 04:21:48PM -0300, Simon Martin wrote:
Thanks Konrad,
Thursday, November 13, 2014, 4:03:38 PM, you wrote:
Yes I do verify the write. How do I check this from Dom0?
You can crank up the debug
On 18.11.14 at 17:24, furryfutt...@gmail.com wrote:
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
Hi all,
I am back on my virtual machine once again and have run into a bit of
a problem (once again). So I am coming to you cap in hand...
I am having 2 major problems at the moment.
1.- Access to the PCI device from the PV will fail the second time I
create it UNLESS I call xl
Hello Jan,
Yes, the first thing I do in the driver is set the PCI configuration
access bits to 7 that should enable IO space, Memory Space and Master
BUS access.
As a test I disabled this and all reads to the PCI device return -1,
even the first one.
I implied your earlier
