From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Kenneth Wong <kenwong@marvell.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Loading PCIe Device Driver at Dom0
Date: Fri, 25 May 2012 16:30:33 -0400 [thread overview]
Message-ID: <20120525203033.GC23655@phenom.dumpdata.com> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2EFB6C3D@SC-VEXCH4.marvell.com>
On Thu, May 24, 2012 at 07:37:44PM -0700, Kenneth Wong wrote:
> Hi Konrad,
>
> > Um, does your driver have a PCI vendor and model? It would
> > do it from the struct pci_driver->probe function.
>
> Yeah, it has all that. It has been running fine on regular Linux, just that problems start coming up when porting to Xen env. I think because it is now less forgiving due to the virtualization layer.
Sure. It also means that your driver would not work with IOMMU's properly.
>
> Any idea on the following messages?
Some, but without any details (like machine type, userspace version, Xorg version,
kernel version, Xorg.0.log, etc) I've no clue.
>
> Xorg[1234]: segfault at 34 ip 00000000005067b1 sp 00007fff37a82f40 error 4 in Xorg[400000+1d4000]
> rtkit-daemon[1708]: segfault at ffffffffffffff80 ip 00007fe23abee61a sp 00007fff9c249410 error 4 in libdbus-1.so.3.5.7[7fe23abc3000+42000]
>
> I think this might be cause by some other things in the driver.
So you see this only after you load your driver?
next prev parent reply other threads:[~2012-05-25 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 23:43 Loading PCIe Device Driver at Dom0 Kenneth Wong
2012-05-24 0:17 ` Konrad Rzeszutek Wilk
2012-05-24 2:41 ` Kenneth Wong
2012-05-24 6:18 ` Pasi Kärkkäinen
2012-05-24 7:10 ` Kenneth Wong
2012-05-24 23:21 ` Kenneth Wong
2012-05-25 0:07 ` Kenneth Wong
2012-05-25 1:34 ` Konrad Rzeszutek Wilk
2012-05-25 2:37 ` Kenneth Wong
2012-05-25 20:30 ` Konrad Rzeszutek Wilk [this message]
2012-05-25 21:12 ` Kenneth Wong
2012-05-25 21:11 ` Xorg crashes... with what distro? Konrad Rzeszutek Wilk
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=20120525203033.GC23655@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kenwong@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).