From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: early_cpu_init() and identify_cpu() Date: Tue, 17 Jul 2007 08:55:08 +0100 Message-ID: References: <20070716102329.62b8bf17@the-village.bc.nu> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070716102329.62b8bf17@the-village.bc.nu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alan Cox , Jan Beulich Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 16/7/07 10:23, "Alan Cox" 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