On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote: > > > qxl surfaces (used for framebuffers and gem objects) can live in both > > VRAM and PRIV ttm domains. Update placement setup to include both. Put > > PRIV first in the list so it is preferred, so VRAM will have more room > > for objects which must be allocated there. > > > > Signed-off-by: Gerd Hoffmann <kraxel@xxxxxxxxxx> > > I remember these kind of changes in the past made migration > fails. I proposed similar patches years ago and they were rejected > for these reasons. Pointer? > Why now they are safe? Well, you have to be careful what object you are allocating. Surfaces can be in both PRIV and VRAM. Everything else (qxl commands, monitors config, ...) must be in VRAM. > Looks like we are improving QXL, so that means we are actively working > on it. Well, I'm just trying make qxl behave better with wayland. > Should we not then thinking about moving feature in the proper > places (like spice-server for atomic mode setting instead of implementin > work around) ?? Main advantage is that it doesn't need qxl device changes, so it works on old hosts too. But, yes, we can consider to also modernize spice protocol and qxl device. cheers, Gerd _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
