From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Widawsky Subject: Re: [PATCH 1/5] drm/vgem: virtual GEM provider Date: Mon, 20 Feb 2012 18:10:07 +0100 Message-ID: <20120220181007.04ba20fe@intel.com> References: <1328743171-13750-2-git-send-email-ben@bwidawsk.net> <959188052.1150535.1329400331995.JavaMail.root@zimbra-prod-mbox-2.vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from azsmga102.ch.intel.com (mga12.intel.com [143.182.124.36]) by gabe.freedesktop.org (Postfix) with ESMTP id 918059E902 for ; Mon, 20 Feb 2012 09:21:06 -0800 (PST) Received: by werl4 with SMTP id l4so3363604wer.25 for ; Mon, 20 Feb 2012 09:11:14 -0800 (PST) In-Reply-To: <959188052.1150535.1329400331995.JavaMail.root@zimbra-prod-mbox-2.vmware.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Jakob Bornecrantz Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Thu, 16 Feb 2012 05:52:12 -0800 (PST) Jakob Bornecrantz wrote: > ----- Original Message ----- > > From: Adam Jackson > > > > This is about as minimal of a virtual GEM service as possible. My > > plan is to use this with non-native-3D hardware for buffer sharing > > between X and DRI. > > > > The current drisw winsys assumes an unmodified X server, which means > > it's hopelessly inefficient for both the push direction of > > SwapBuffers/DrawPixels and the pull direction of > > GLX_EXT_texture_from_pixmap. I'm still working through the details > > of what the xserver support will look like, but in broad strokes it's > > "use vgem for CreatePixmap and optionally the shadowfb". > > > > Obviously alpha quality, mostly looking for feedback on the approach > > or any glaring bugs. Eventually I'd like to see solutions for > > sharing gem objects between drm devices and/or the dma_buf API, but > > that's a ways down the road. > > > > Signed-off-by: Adam Jackson > > Any reason why you are not using the dumb_bo interface? I at least > would like to be able to offer vgem on the vmwgfx device when the > host has disabled 3D. > > Cheers, Jakob. I thought dumb bo interface was an extension for an existing DRM GEM driver. In my case, for prototyping dma_buf support, this is non-ideal. I'm not sure what Adam thinks of this though (I imagine he wants a device independent driver though). I may be completely off.