[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] early_cpu_init() and identify_cpu()
On 17/7/07 10:58, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote: >>> That's a win of about 30%, and using movsq in memcpy() is another win of >>> about 50%. Will probably create a vidmemmove()... >> >> That still totally sucks then. Paging a full screen of text of, say 60 >> lines, done line-by-line will still take, say 60*300ms == 20 seconds(ish). > > No, you got me wrong - with 'scrolling by one line' I mean the scrolling the > entire screen up by a line. It's about half as fast as Linux during boot now, > visibly slower post-boot. Re-draw is going to be the default, even if I have to implement it on top of your patch. :-) The fact that dom0 will overwrite Xen's output anyway as it re-draws seems to make scrolling-as-default the inferior option because it's significantly slower and can provide benefit really only for crash dumps (where a re-draw based scheme can work just as well). So I don't understand your attachment to scrolling. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |