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] early_cpu_init() and identify_cpu()

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] early_cpu_init() and identify_cpu()
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 17 Jul 2007 08:55:08 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Jul 2007 00:53:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070716102329.62b8bf17@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfIR8soCdgW2jQ7EdykoQAX8io7RQ==
Thread-topic: [Xen-devel] early_cpu_init() and identify_cpu()
User-agent: Microsoft-Entourage/11.3.3.061214
On 16/7/07 10:23, "Alan Cox" <alan@xxxxxxxxxxxxxxxxxxx> wrote:

>> significant (though I assume WC would at best help a little, I'm considering
>> other approaches, too): Scrolling a 1280x1024x16 screen takes, on the test
>> system I'm primarily trying this out on, on the order of a second. This is
> 
> A lot of work on this has been done in X by the X and Gnome developers
> including producing some routines which use the largest possible aligned
> loads to reduce the big cost (which is PCI reads). Having a write
> combining video memory can help (but some cards also put stuff like
> command queues there which X cannot WC).

Does this mean that defaulting to setting up WC on a power-of-two-sized
region starting at the framebuffer address is not really safe on a fair
number of systems?

 -- Keir


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