Re: [PATCH v2] drm/amdgpu: avoid using null object of framebuffer

On 2024/6/19 12:53, Huang Rui wrote: On Wed, Jun 19, 2024 at 12:46:25PM +0800, Huang Rui wrote: On Wed, Jun 19, 2024 at 12:29:24PM +0800, Zhang, Julia wrote: Instead of using state->fb->obj[0] directly, get object from framebuffer by calling drm_gem_fb_get_obj() and return error cod

Re: [PATCH v2 1/1] drm/virtio: Implement device_attach

On 2024/1/30 22:23, Christian König wrote: > Am 30.01.24 um 12:16 schrieb Daniel Vetter: >> On Tue, Jan 30, 2024 at 12:10:31PM +0100, Daniel Vetter wrote: >>> On Mon, Jan 29, 2024 at 06:31:19PM +0800, Julia Zhang wrote: As vram objects don't have backing pages and thus can't implement d

Re: [PATCH 1/1] drm/virtio: Implement device_attach

On 2024/1/10 18:21, Daniel Vetter wrote: > On Wed, Jan 10, 2024 at 05:56:28PM +0800, Julia Zhang wrote: >> drm_gem_map_attach() requires drm_gem_object_funcs.get_sg_table to be >> implemented, or else return ENOSYS. Virtio has no get_sg_table >> implemented for vram object. To fix this, add a new

Re: [PATCH 1/1] drm/virtio: Implement RESOURCE_GET_LAYOUT ioctl

On 2024/1/10 18:47, Daniel Vetter wrote: > On Thu, Dec 21, 2023 at 06:00:16PM +0800, Julia Zhang wrote: >> From: Daniel Stone >> >> Add a new ioctl to allow the guest VM to discover how the guest >> actually allocated the underlying buffer, which allows buffers to >> be used for GL<->Vulkan inte

Re: [PATCH v2 0/1] Implementation of resource_query_layout

I see, I will implement this. Thank you very much. On 2023/12/27 09:29, Gurchetan Singh wrote: > > > On Thu, Dec 21, 2023 at 2:01 AM Julia Zhang > wrote: > > Hi all, > > Sorry to late reply. This is v2 of the implementation of > resource_query_layout. T