----- "Dave Airlie" <airl...@gmail.com> wrote: > >> I haven't had much time to review the code, but it would be nice if > we > >> could > >> start a qxl interface document that isn't qxl.h, something > specifying > >> behaviour, > >> > >> The main thing I'm wondering is how the guest sees these offscreen > >> surfaces? > > > > It is the guest drive responsiebility to allocat surfaces/textures > except > > for surf0 that is special case. Surf0 is shared with the VGA > subsytem in order > > to reduce memmory usage. All other surfaces will be allocated by the > driver > > from pci mem or alternatively from guest ram. Allocaiton from guest > ram > > (guest mem slots) must use consecutive guest physical ram. > > > > I think this shouldn't be necessary though, it should be possible to
Sure it is possible but we have more important tasks to do. Consecutive guest physical ram came without a real cost for that reason we'll support it. Additionally QXL ram size can be change during startaup so in case of need we can instruct the user to increase QXL ram size. Yaniv > s/g the > guest physical RAM, we can then use a kernel driver to provide linear > maps > in userspace on the guest, and vmaps in kernel. > > I expect getting contiguous pages in the guest may be an issue same > as it is on physical hw. > > Dave. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Spice-space-devel mailing list Spice-space-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spice-space-devel
