From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Loading PCIe Device Driver at Dom0 Date: Fri, 25 May 2012 16:30:33 -0400 Message-ID: <20120525203033.GC23655@phenom.dumpdata.com> References: <20120524001712.GA6285@phenom.dumpdata.com> <20120524061806.GX2058@reaktio.net> <20120525013421.GC20947@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Kenneth Wong Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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?