From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org, spice-devel@freedesktop.org,
Dave Airlie <airlied@redhat.com>
Subject: Re: [Qemu-devel] [Spice-devel] viewing continuous guest virtual memory as continuous in qemu
Date: Tue, 11 Oct 2011 15:20:24 +0200 [thread overview]
Message-ID: <4E944298.1010409@redhat.com> (raw)
In-Reply-To: <20111011121529.GA1049@bow.tlv.redhat.com>
Hi,
>> Another option we can think about is a 64bit PCI bar for the
>> surfaces which can be moved out of the low 4G.
>
> I heard this suggested by Avi, so this would allow us to allocate a
> large chunk without requiring any memory hole?
You still need some address space for it, but as it isn't limited to
32bit addresses it can be mapped somewhere above 4G, i.e. we don't have
to squeeze it into the 512MB pci hole at 0xe0000000. We can easily
create a qxl gfx card with 1G of vram (aka surface) memory.
Only question is how to handle that in a backward compatible way. We
have regions 4+5 in pci config space still unused. 64bit bars need two
entries, so adding a 64bit bar would use up both. The new 64bit vram
bar would cover all vram memory. The old 32bit vram bar would be a
window to the first 32 or 64 MB of vram memory. We could probably even
create some register to make the 32bit bar window offset configurable,
so you can access all vram memory using the 32bit bar, just not all at
the same time. Not sure the latter is worth the effort with the world
moving to 64bit.
cheers,
Gerd
prev parent reply other threads:[~2011-10-11 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 13:24 [Qemu-devel] viewing continuous guest virtual memory as continuous in qemu Alon Levy
2011-10-02 14:31 ` [Qemu-devel] [Spice-devel] " 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 [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=4E944298.1010409@redhat.com \
--to=kraxel@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).