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: Thu, 13 Nov 2014 14:49:07 -0300 [thread overview]
Message-ID: <429773295.20141113144907@gmail.com> (raw)
In-Reply-To: <5464E1D9020000780004746B@mail.emea.novell.com>
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 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?
>> I agree, this looks more than a hang than a crash. I've just found a
>> link to the USB debug cable. I've ordered one but it will take a while
> And I hope you first verified that your system meets the criteria
> for this to work in the first place?
I followed the checks in the Kernel earlyprintk debugging HOWTO, i.e.
lspci -vvv to check the USB debug capability, and it verified. The
device is ordered and now just to wait....
--
Best regards,
Simon mailto:furryfuttock@gmail.com
next prev parent reply other threads:[~2014-11-13 17:49 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 [this message]
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
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=429773295.20141113144907@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.