From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6965] Implement and use shared memory framebuffer device rendering reoutine.
Date: Thu, 2 Apr 2009 22:33:06 +0000 [thread overview]
Message-ID: <200904022333.06627.paul@codesourcery.com> (raw)
In-Reply-To: <fb249edb0904021352s7bc2f7aaye63a7ada10dd7d1b@mail.gmail.com>
> If we must use the map/unmap api for framebuffers (even though we know
> this memory is continuous in qemu) then we could map only the region
> we determined is dirty.
Maybe. In practice I doubt there's that much difference. In general we don't
actually know the memory is contiguous, though for well behaved guests with
current boards it probably is. The proper solution is probably to replace
l1_phys_map with an extent bases system, so that map time is not proportional
to region size.
My main motivation for this patch is that it is the first step in eliminating
phys_ram_base.
Paul
prev parent reply other threads:[~2009-04-02 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 12:28 [Qemu-devel] [6965] Implement and use shared memory framebuffer device rendering reoutine Paul Brook
2009-04-02 20:52 ` andrzej zaborowski
2009-04-02 22:33 ` Paul Brook [this message]
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=200904022333.06627.paul@codesourcery.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).