On Fri, Feb 28, 2020 at 01:01:49PM -0800, Chia-I Wu wrote:
On Wed, Oct 2, 2019 at 5:18 PM Gurchetan Singh gurchetansingh@chromium.org wrote:
On Wed, Oct 2, 2019 at 1:49 AM Gerd Hoffmann kraxel@redhat.com wrote:
On Tue, Oct 01, 2019 at 06:49:35PM -0700, Gurchetan Singh wrote:
This doesn't really break userspace, since it always passes down 0 for stride/layer_stride currently. We could:
(1) modify UAPI now and add a VIRTGPU_PARAM_STRIDE_FIX feature
This I think. But IMO it's not a fix, it is an added feature ...
Also missing the big picture here. Why do we need this?
Two reasons:
I don't fully get the picture, but drm_virtgpu_resource_create has stride. Can we send that down in transfers?
It's unused and suddenly caring about it has a good chance to break stuff ...
cheers, Gerd