17:29 <MoeIcenowy> I see some padding added in pvr_GetBufferMemoryRequirements2(), which isn't compatible the current Mesa WSI common code

17:30 <MoeIcenowy> (I am now hacking on TH1520 SoC, on which I can have DRI3 by using Xorg + etnaviv 2D acceleration, so I am trying out more WSI)

17:31 <MoeIcenowy> which address space is the padding trying to prevent read-across-page in? device address space or cpu address space?

17:31 <MoeIcenowy> (I think for compatibility of common WSI code the "map one more page" practice might be needed

17:32 <MoeIcenowy> (the reason of incompatibility is common WSI code is asserting the required buffer size being not larger than the size it calculated

17:34 <MoeIcenowy> P.S. current driver acquires num_phantoms from kernel, but the device info has num_clusters too

17:35 <MoeIcenowy> I think this is duplicated?

17:41 <MoeIcenowy> and for mapping an extra page, if it's to be prevent issues of device address space, should the preventing code be in kernel driver?

17:42 <MoeIcenowy> (this will sounds a burden to let the userspace to know whether such a workaround exists