WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [Code Trace] dom0 Nouveau accelerated mmap problem

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Code Trace] dom0 Nouveau accelerated mmap problem
From: Arvind R <arvino55@xxxxxxxxx>
Date: Sun, 28 Feb 2010 13:01:16 +0530
Cc: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Sat, 27 Feb 2010 23:32:01 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=EDgHtspz0Egrzm3BK97zadYovEIvI4o656GU/4CfFyc=; b=Aasm4VKFze3ITr8tWYDlFCqwPXu2gU75fHgfzONId0c1hz0h9h3EaUftzFYHorDDoF gbAoomjTg69iyY1PcnWHpFtV8aSck8Nnb2adiL4nd+E68zW5fL5DkEIcRMrew303JhKA wqYw6Sh44MUJboGADgg+oLKSJAa+k2mfVbKJM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=c8ML+itKPFCURVQejI0BlVk/a4ZASZYe5jrNFbQYPDd5F878x1eIi36/fodcrRo+Kf V4D/HrkxcK6cCm38iavbof1wgRGLW/0MRgcEVaJR/QJJMXsS+lgcYSJLhbiBEZLF0pPC 6LYEM88CwlxNc5LLSM/2qcsYCp+wx4/+kF5mQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
In continuation of my 'Nouveau on dom0' posting, I dug into the code ...
As Konrad had predicted, it is the discontinuous PFN in the mmapped
area that seems to the problem.

booted bare hardware
X: libdrm:OUT_RING: Enter: chan=0x8170a0, id=2, data=0x44000,
chan->cur=0x7fcdaff5e000
*(chan->cur++) = (data);
X: libdrm:OUT_RING: Exit
<some time later>
kernel: ttm_bo_vm_fault: bo=ffff88007ccfb200
kernel: ttm_bo_vm_fault: is_iomem=0, page_offset=0x0, page_last=0x10,
bo->num_pages=16
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff5e000,
pfn=0x73f95, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff5f000,
pfn=0x73f96, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff60000,
pfn=0x73f97, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff61000,
pfn=0x73f98, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff62000,
pfn=0x73f99, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff63000,
pfn=0x73f9a, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff64000,
pfn=0x73f9b, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff65000,
pfn=0x73f9c, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff66000,
pfn=0x73f9d, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff67000,
pfn=0x73f9e, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff68000,
pfn=0x73f9f, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff69000,
pfn=0x73fa0, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6a000,
pfn=0x73fa1, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6b000,
pfn=0x73fa2, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6c000,
pfn=0x73fa3, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88007b493870, address=0x7fcdaff6d000,
pfn=0x73fa4, ret=0

booted Xen
X: libdrm:OUT_RING: Enter: chan=0x8170a0, id=2, data=0x44000,
chan->cur=0x7faed9add000
<some time later, repeats never-ending till shutdown, OUT_RING never exits>
kernel: ttm_bo_vm_fault: bo=ffff88000e79ba00
kernel: ttm_bo_vm_fault: is_iomem=0, page_offset=0x0, page_last=0x10,
bo->num_pages=16
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9add000,
pfn=0xe6db, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ade000,
pfn=0xe718, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9adf000,
pfn=0xe772, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae0000,
pfn=0xe778, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae1000,
pfn=0xe6eb, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae2000,
pfn=0xe738, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae3000,
pfn=0xe6da, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae4000,
pfn=0xe710, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae5000,
pfn=0xe76e, ret=0
kernel: ttm_bo_vm_fault: vma=ffff88000e691918, address=0x7faed9ae6000,
pfn=0xe7ad, ret=0

ttm_bo_vm_fault() is in drivers/gpu/drm/ttm/ttm_bo_vm.c in the kernel tree.

HELP!
Arvind R.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [Code Trace] dom0 Nouveau accelerated mmap problem, Arvind R <=