From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-5456-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 157E0985B8C for ; Tue, 19 Feb 2019 07:18:05 +0000 (UTC) Date: Tue, 19 Feb 2019 08:17:56 +0100 From: Gerd Hoffmann Message-ID: <20190219071756.f5qayejwls66jjhb@sirius.home.kraxel.org> References: <20190204054053.GE29758@stefanha-x1.localdomain> <20190204101316.4e3e6rj32suwdmur@sirius.home.kraxel.org> <20190211092943-mutt-send-email-mst@kernel.org> <20190212131638.GF2715@work-vm> <20190212082555-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [virtio-dev] Memory sharing device To: Frank Yang Cc: "Michael S. Tsirkin" , "Dr. David Alan Gilbert" , Roman Kiryanov , Stefan Hajnoczi , virtio-dev@lists.oasis-open.org List-ID: On Tue, Feb 12, 2019 at 08:17:13AM -0800, Frank Yang wrote: > In implementing a complete graphics system, shared memory objects may > transcend device boundaries. > > Consider for example, Android and gralloc. The media codec versus the GPU > rendering are commonly considered as separate devices, but they work better > if operating on a common shared memory type (gralloc buffers). Linux has dma-bufs for that (driver-api/dma-buf.rst). cheers, Gerd --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org