Re: [Freedreno] [PATCH] drm/msm: Optimize GPU crashstate capture read path

2018-11-02 Thread Jordan Crouse
On Fri, Nov 02, 2018 at 03:12:51PM +0530, Sharat Masetty wrote: > Thanks for the comments Jordan - > > On 11/1/2018 8:34 PM, Jordan Crouse wrote: > >On Thu, Nov 01, 2018 at 02:05:41PM +0530, Sharat Masetty wrote: > >>When the userspace tries to read the crashstate dump, the read side > >>implement

Re: [Freedreno] [PATCH] drm/msm: Optimize GPU crashstate capture read path

2018-11-02 Thread Sharat Masetty
Thanks for the comments Jordan - On 11/1/2018 8:34 PM, Jordan Crouse wrote: On Thu, Nov 01, 2018 at 02:05:41PM +0530, Sharat Masetty wrote: When the userspace tries to read the crashstate dump, the read side implementation in the driver currently ascii85 encodes all the binary buffers and it do

Re: [PATCH] drm/msm: Optimize GPU crashstate capture read path

2018-11-01 Thread Jordan Crouse
On Thu, Nov 01, 2018 at 02:05:41PM +0530, Sharat Masetty wrote: > When the userspace tries to read the crashstate dump, the read side > implementation in the driver currently ascii85 encodes all the binary > buffers and it does this each time the read system call is called. > A userspace tool like

[PATCH] drm/msm: Optimize GPU crashstate capture read path

2018-11-01 Thread Sharat Masetty
When the userspace tries to read the crashstate dump, the read side implementation in the driver currently ascii85 encodes all the binary buffers and it does this each time the read system call is called. A userspace tool like cat typically does a page by page read and the number of read calls depe