From: Jamie Lokier <jamie@shareable.org>
To: Nathan Baum <nathan@parenthephobia.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] File-backed memory maps
Date: Fri, 18 Sep 2009 14:59:07 +0100 [thread overview]
Message-ID: <20090918135906.GB1631@shareable.org> (raw)
In-Reply-To: <1253275896.11717.239.camel@localhost.localdomain>
Nathan Baum wrote:
> makes two files named "prefix.vga" and "prefix.bios" which contain the
> respective memory regions. The maps I've named are 640k, before_4g,
> after_4g, vga, bios and option_rom.
>
> I'm mainly interested in the idea of moving the VNC server into its own
> process. It would listen for connections as usual and then send
> framebuffer updates from the file. Doing that also requires a
> side-channel for communicating graphics mode updates and peripheral
> input between QEMU and the VNC server. (Something like "-mouse
> <char-dev-spec> -keyboard <char-dev-spec>", perhaps?)
Are there any cache coherency issues?
On architectures other than x86, sometimes data written by one process
is not visible to another process mapping the same file, until the
writing process flushes it's cache for those pages. Whether that's
necessary depends on the address that pages are mapped to. Afaik,
normally Linux chooses an address where this issue is avoided, but if
you specify it with MAP_FIXED (or whatever KVM does to map pages),
then there's cache coherency to deal with.
-- Jamie
next prev parent reply other threads:[~2009-09-18 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 12:11 [Qemu-devel] [RFC][PATCH] File-backed memory maps Nathan Baum
2009-09-18 13:59 ` Jamie Lokier [this message]
2009-09-18 15:05 ` Nathan Baum
2009-09-18 16:10 ` Jamie Lokier
2009-09-18 15:15 ` Anthony Liguori
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=20090918135906.GB1631@shareable.org \
--to=jamie@shareable.org \
--cc=nathan@parenthephobia.org.uk \
--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).