From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-5368-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id CD4CD985A3D for ; Mon, 4 Feb 2019 10:18:44 +0000 (UTC) MIME-Version: 1.0 References: <20190204054053.GE29758@stefanha-x1.localdomain> <20190204101316.4e3e6rj32suwdmur@sirius.home.kraxel.org> In-Reply-To: <20190204101316.4e3e6rj32suwdmur@sirius.home.kraxel.org> From: Roman Kiryanov Date: Mon, 4 Feb 2019 02:18:31 -0800 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [virtio-dev] Memory sharing device To: Gerd Hoffmann Cc: Stefan Hajnoczi , virtio-dev@lists.oasis-open.org, "Dr. David Alan Gilbert" List-ID: > > David Gilbert, Gerd Hoffmann, and I have discussed adding shared memory > > resources to VIRTIO. That means memory made available by the device to > > the driver instead of the usual other way around. > > > > virtio-gpu needs this and perhaps that use case overlaps with yours too. > > virtio-gpu specifically needs that to support vulkan and opengl > extensions for coherent buffers, which must be allocated by the host gpu > driver. It's WIP still. Thank you, Stefan and Gerd for looking into it. Yes, Vulkan is our first use case for the memory sharing device. I will take a look to the draft Stefan provided to see how it is different from what we are thinking about. Regards, Roman. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org