From: Keir Fraser <keir@xensource.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: early_cpu_init() and identify_cpu()
Date: Tue, 17 Jul 2007 08:55:08 +0100 [thread overview]
Message-ID: <C2C2346C.128BF%keir@xensource.com> (raw)
In-Reply-To: <20070716102329.62b8bf17@the-village.bc.nu>
On 16/7/07 10:23, "Alan Cox" <alan@lxorguk.ukuu.org.uk> 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
next prev parent reply other threads:[~2007-07-17 7:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 16:16 early_cpu_init() and identify_cpu() Jan Beulich
2007-07-13 16:26 ` Keir Fraser
2007-07-16 6:14 ` Jan Beulich
2007-07-16 6:25 ` Keir Fraser
2007-07-16 6:41 ` Jan Beulich
2007-07-16 6:57 ` Keir Fraser
2007-07-16 7:01 ` Keir Fraser
2007-07-16 7:31 ` Jan Beulich
2007-07-16 7:30 ` Jan Beulich
2007-07-16 9:23 ` Alan Cox
2007-07-17 7:55 ` Keir Fraser [this message]
2007-07-17 10:00 ` Jan Beulich
2007-07-17 10:15 ` Keir Fraser
2007-07-17 10:23 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2007-07-16 8:18 Jan Beulich
2007-07-17 7:50 ` Keir Fraser
2007-07-17 9:58 ` Jan Beulich
2007-07-17 10:05 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2C2346C.128BF%keir@xensource.com \
--to=keir@xensource.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.