From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pci passthrough xhci host controller
Date: Mon, 20 Sep 2010 16:33:44 -0400 [thread overview]
Message-ID: <20100920203344.GA26201@dumpdata.com> (raw)
In-Reply-To: <1262837074.20100915230935@eikelenboom.it>
On Wed, Sep 15, 2010 at 11:09:35PM +0200, Sander Eikelenboom wrote:
> Hi Konrad,
>
> I have changed my setup a bit, using my old workstation as a xen test platform at the moment.
>
> I'm now running:
> - Xen-unstable xen_changeset : Fri Sep 10 19:06:33 2010 +0100 22132:3985fea87987
> - Dom0: pvops stable-2.6.32.x last commit b297cdac0373625d3cd0e6f2b393570dcf2edba6
> - DomU: Own merge of:
> -linus 2.6.36(-rc4) tree last commit 9c03f1622af051004416dd3e24d8a0fa31e34178
> -your pci-front 0.6 tree
>
> - Only one domU is running (copy of the one i used before on the other machine)
> - Only one pci-e xhci hostcontroller is passed through (02:00.0)
> - domU is booted with only iommu-soft
>
> What happens:
> - domU boots fine, pci device is present, lsusb shows the card, but the grab util can't find the grabber on /dev/video0
> - The app keeps on trying ..
What was the error with the /dev/video0?
The same as before where the em_8xx died in a horrible death?
> - What i do see is a continuing stream of suspected kmemleaks in the domU
Hmm.. They aren't huge, they are actually all quite small (64 bytes and 32 bytes).
That is all that happens when DomU dies due to OOM going wild?
next prev parent reply other threads:[~2010-09-20 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 21:09 pci passthrough xhci host controller Sander Eikelenboom
2010-09-20 20:33 ` Konrad Rzeszutek Wilk [this message]
2010-09-21 20:03 ` Sander Eikelenboom
2010-09-27 15:59 ` Konrad Rzeszutek Wilk
2010-09-27 20:35 ` Sander Eikelenboom
2010-09-30 19:24 ` Sander Eikelenboom
2010-10-01 20:54 ` Konrad Rzeszutek Wilk
2010-10-01 23:33 ` Sander Eikelenboom
2010-10-02 17:44 ` Sander Eikelenboom
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=20100920203344.GA26201@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
/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.