Re: drm/virtio: not pin pages on demand

2021-10-28 Thread Chia-I Wu
On Wed, Oct 27, 2021 at 4:12 AM Gerd Hoffmann wrote: > > [ Cc'ing Gurchetan Singh ] > > > Can we follow up on this issue? > > > > The main pain point with your suggestion is the fact, > > that it will cause VirGL protocol breakage and we would > > like to avoid this. > > > > Extending execbuffer i

Re: drm/virtio: not pin pages on demand

2021-10-27 Thread Gerd Hoffmann
[ Cc'ing Gurchetan Singh ] > Can we follow up on this issue? > > The main pain point with your suggestion is the fact, > that it will cause VirGL protocol breakage and we would > like to avoid this. > > Extending execbuffer ioctl and create_resource ioctl is > more convenient than having the pro

Re: drm/virtio: not pin pages on demand

2021-10-27 Thread Maksym Wezdecki
Gerd, Can we follow up on this issue? The main pain point with your suggestion is the fact, that it will cause VirGL protocol breakage and we would like to avoid this. Extending execbuffer ioctl and create_resource ioctl is more convenient than having the protocol broken. Blob resources is not

Re: drm/virtio: not pin pages on demand

2021-10-22 Thread Maksym Wezdecki
On 10/21/21 6:42 PM, Chia-I Wu wrote: > On Thu, Oct 21, 2021 at 4:52 AM Gerd Hoffmann wrote: >> On Thu, Oct 21, 2021 at 11:55:47AM +0200, Maksym Wezdecki wrote: >>> I get your point. However, we need to make resource_create ioctl, >>> in order to create corresponding resource on the host. >> That

Re: drm/virtio: not pin pages on demand

2021-10-22 Thread Maksym Wezdecki
Once again with all lists and receivers. I'm sorry for that. On 10/21/21 6:42 PM, Chia-I Wu wrote: > On Thu, Oct 21, 2021 at 4:52 AM Gerd Hoffmann wrote: >> On Thu, Oct 21, 2021 at 11:55:47AM +0200, Maksym Wezdecki wrote: >>> I get your point. However, we need to make resource_create ioctl, >>> i

Re: drm/virtio: not pin pages on demand

2021-10-21 Thread Chia-I Wu
On Thu, Oct 21, 2021 at 4:52 AM Gerd Hoffmann wrote: > > On Thu, Oct 21, 2021 at 11:55:47AM +0200, Maksym Wezdecki wrote: > > I get your point. However, we need to make resource_create ioctl, > > in order to create corresponding resource on the host. > > That used to be the case but isn't true any

Re: drm/virtio: not pin pages on demand

2021-10-21 Thread Maksym Wezdecki
I get your point. However, we need to make resource_create ioctl, in order to create corresponding resource on the host. The concept is: App |Gallium | Guest kernel What is happening? init() ...... glTexImage2

Re: drm/virtio: not pin pages on demand

2021-10-21 Thread Gerd Hoffmann
On Thu, Oct 21, 2021 at 11:55:47AM +0200, Maksym Wezdecki wrote: > I get your point. However, we need to make resource_create ioctl, > in order to create corresponding resource on the host. That used to be the case but isn't true any more with the new blob resources. virglrenderer allows to creat

Re: drm/virtio: not pin pages on demand

2021-10-21 Thread Gerd Hoffmann
On Thu, Oct 21, 2021 at 09:44:45AM +0200, Maksym Wezdecki wrote: > From: mwezdeck > > The idea behind the commit: > 1. when resource is created, let user space decide > if resource should be pinned or not > 2. transfer_*_host needs pinned memory. If it is not > pinned, then pin it.

drm/virtio: not pin pages on demand

2021-10-21 Thread Maksym Wezdecki
From: mwezdeck The idea behind the commit: 1. when resource is created, let user space decide if resource should be pinned or not 2. transfer_*_host needs pinned memory. If it is not pinned, then pin it. 3. during execbuffer, decide which bo handles should be pinned based on