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

Re: [Xen-devel] Frame buffer mmap not working in pvops dom0

To: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Frame buffer mmap not working in pvops dom0
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 21 Jul 2010 17:16:13 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 21 Jul 2010 07:18:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C46FA8D.6040809@xxxxxxxxxxxxx>
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>
References: <4C46FA8D.6040809@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Jul 21, 2010 at 09:47:57AM -0400, Daniel De Graaf wrote:
> I'm trying to confirm the fix to the VESA fbdev mmap issue that was
> brought up a few months ago
> (http://marc.info/?l=xen-devel&m=126842551306571&w=2). The wiki page at
> http://wiki.xensource.com/xenwiki/XenPVOPSDRM says that this bug should
> be fixed, but doesn't point to a patch for the fix. I am still able to
> reproduce the issue both on real hardware and by running Xen under qemu
> (using cirrusfb on the dom0). Eamon (the original reporter) has also not
> been able to confirm a fix.
> 
> I'm currently testing using Xen 4.1 built from hg 21831:6bebaf40e925 and
> a pvops dom0 from xen/stable-2.6.32.x revid c0a00fbe.
> 
> So far, I've been able to determine that an mmap requesting multiple
> pages from /dev/fb0 will result in page table entries all pointing to
> the same physical page, which is not in the framebuffer address space.
> Writing to the mapped page ends up corrupting parts of kernel memory.
> I'd be happy to run further tests, try patches, or provide more
> information if needed.
> 

I guess many (most?) graphics related fixes are in Konrad's git tree..

-- Pasi


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