qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org, spice-devel@freedesktop.org
Cc: Dave Airlie <airlied@redhat.com>
Subject: [Qemu-devel] viewing continuous guest virtual memory as continuous in qemu
Date: Sun, 2 Oct 2011 15:24:36 +0200	[thread overview]
Message-ID: <20111002132436.GD11521@bow.tlv.redhat.com> (raw)

Hi,

 I'm trying to acheive the $subject. Some background: currently spice relies on a preallocated pci bar for both surfaces and for VGA framebuffer + commands. I have been trying to get rid of the surfaces bar. To do that I allocate memory in the guest and then translate it for spice-server consumption using cpu_physical_memory_map.

 AFAIU this works only when the guest allocates a continuous range of physical pages. This is a large requirement from the guest, which I'd like to drop. So I would like to have the guest use a regular allocator, generating for instance two sequential pages in virtual memory that are scattered in physical memory. Those two physical guest page addresses (gp1 and gp2) correspond to two host virtual memory addresses (hv1, hv2). I would now like to provide to spice-server a single virtual address p that maps to those two pages in sequence. I don't want to handle my own scatter-gather list, I would like to have this mapping done once so I can use an existing library that requires a single pointer (for instance pixman or libGL) to do the rendering.

 Is there any way to acheive that without host kernel support, in user space, i.e. in qemu? or with an existing host kernel device?

 I'd appreciate any help,

Alon

             reply	other threads:[~2011-10-02 13:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 13:24 Alon Levy [this message]
2011-10-02 14:31 ` [Qemu-devel] [Spice-devel] viewing continuous guest virtual memory as continuous in qemu Alon Levy
2011-10-02 17:12   ` Avi Kivity
2011-10-03  7:49     ` Alon Levy
2011-10-03  8:17 ` Yonit Halperin
2011-10-03  8:37   ` Alon Levy
2011-10-03  8:49     ` Alon Levy
2011-10-03 15:10     ` Avi Kivity
2011-10-11 11:28 ` Gerd Hoffmann
2011-10-11 12:21   ` Alon Levy
2011-10-11 13:20     ` Gerd Hoffmann

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=20111002132436.GD11521@bow.tlv.redhat.com \
    --to=alevy@redhat.com \
    --cc=airlied@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@freedesktop.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).