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,
Hi,
> slots by doing so. So for Vulkan, we rely on having one large host visible
> region on the host that is a single region of host shared memory. That, is
> then sub-allocated for the guest. So there is no Vulkan host pointer that
Yes, sub-allocating will be needed for reasonable
On 2019/2/14 下午12:04, Michael S. Tsirkin wrote:
On Thu, Feb 14, 2019 at 11:34:22AM +0800, Jason Wang wrote:
On 2019/2/14 上午1:30, Michael S. Tsirkin wrote:
On Wed, Feb 13, 2019 at 06:33:50PM +0800, Jason Wang wrote:
On 2019/2/13 上午1:35, Michael S. Tsirkin wrote:
On Tue, Feb 12, 2019 at
On 2019/2/15 下午12:23, Michael S. Tsirkin wrote:
On Fri, Feb 15, 2019 at 11:59:55AM +0800, Jason Wang wrote:
On 2019/2/14 上午11:41, Michael S. Tsirkin wrote:
I think it's as simple as increase the avail idx by X? Since descriptor were
used in order, device can just read the next X-1
On Mon, Feb 18, 2019 at 11:52:34AM +0100, Miklos Szeredi wrote:
> Indeed, inotify and friends would need notification support, but at
> the moment no network filesystem has that and the kernel doesn't have
> interfaces for filesystems to provide remote notifications, so this is
> quite theoretical
On Mon, Feb 18, 2019 at 08:22:00AM +0100, Jan Kiszka wrote:
> On 31.01.19 05:14, Michael S. Tsirkin wrote:
> > On Thu, Jan 31, 2019 at 10:36:14AM +0800, Stefan Hajnoczi wrote:
> > > The struct virtio_blk_req->data[] field is a multiple of 512 bytes long
> > > for read and write requests. Flush
