From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Simon Martin <furryfuttock@gmail.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: Problems accessing passthrough PCI device
Date: Thu, 13 Nov 2014 14:29:15 -0500 [thread overview]
Message-ID: <20141113192915.GA12502@laptop.dumpdata.com> (raw)
In-Reply-To: <1747475571.20141113162148@gmail.com>
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 volume in xen-pciback. Recompile the kernel
> > and put '#define DEBUG 1' at the start of the .c files.
>
> > Interestingly enough I saw this issue as well - and it looked to me
> > that Xen pciback was stuck in '7' state (Reconfiguring) and never
> > excited it.
>
> > But I hadn't had a chance to dig in this.
>
> This might be related to something that I reported a while ago, that
> when I shutdown the PV it takes a long time for the corresponding
> Dom0 processes to stop.
>
> I'll set the debug level and see what's going on. That'll be on Monday
> now.
Sure thing. Thank you for reporting it!
>
>
> --
> Best regards,
> Simon mailto:furryfuttock@gmail.com
>
next prev parent reply other threads:[~2014-11-13 19:29 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 [this message]
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=20141113192915.GA12502@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=furryfuttock@gmail.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.