From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] Variable video ram size option
Date: Thu, 15 Jan 2009 18:36:12 +0100 [thread overview]
Message-ID: <496F740C.7000405@redhat.com> (raw)
In-Reply-To: <20090115162347.GA5440@shareable.org>
Jamie Lokier wrote:
> I don't know why "ypan" is off by default;
Performance. When reaching the end of video memory ypan does a memcpy
on the framebuffer. ywrap doesn't need the memcpy, but doesn't work on
all hardware. The memcpy is painful slow because framebuffer *read*
access isn't something gfx cards are optimized for.
> If you're using Linux guest with VESA framebuffer console, rather than
> a text-mode console, I'd recommend kernel boot option "video=vesafb:ypan",
> to save considerable CPU when scrolling the console.
Should work inside qemu because you should not face the slow-reads issue
then. On real hardware it very likely makes scrolling noticeable slower.
cheers,
Gerd
next prev parent reply other threads:[~2009-01-15 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 19:13 [Qemu-devel] [PATCH] [RFC] Variable video ram size option Trolle Selander
2009-01-14 20:07 ` Paul Brook
2009-01-14 20:41 ` Trolle Selander
2009-01-14 21:30 ` Paul Brook
2009-01-14 22:47 ` Trolle Selander
2009-01-15 13:08 ` Jamie Lokier
2009-01-15 15:37 ` Rene Rebe
2009-01-15 16:23 ` Jamie Lokier
2009-01-15 17:36 ` Gerd Hoffmann [this message]
2009-01-15 20:57 ` Jamie Lokier
2009-01-15 21:41 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2009-01-09 19:45 Trolle Selander
2009-01-10 0:02 ` Paul Brook
2009-01-10 1:26 ` Trolle Selander
2009-01-10 6:45 ` Blue Swirl
[not found] ` <4967E7D7.4040605@eu.citrix.com>
[not found] ` <200901091716.00827.paul@codesourcery.com>
2009-01-10 1:27 ` Trolle Selander
[not found] ` <4967ECA7.6040809@eu.citrix.com>
[not found] ` <200901091747.06462.paul@codesourcery.com>
2009-01-10 1:28 ` Trolle Selander
2009-01-10 1:47 ` Jamie Lokier
2009-01-11 7:53 ` Avi Kivity
2009-01-12 17:43 ` Trolle Selander
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=496F740C.7000405@redhat.com \
--to=kraxel@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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.