On Thu, 22 Jul 2021 09:48:00 -0400 Sean Paul sean@poorly.run wrote:
On Thu, Jul 22, 2021 at 3:49 AM Pekka Paalanen ppaalanen@gmail.com wrote:
On Wed, 21 Jul 2021 13:55:07 -0400 Sean Paul sean@poorly.run wrote:
From: Sean Paul seanpaul@chromium.org
Hi all, I just had the pleasure of rebasing this set on our CrOS downstream kernel and wanted to resend it for consideration once again. There hasn't been any resistence to the set AFAIK, just perhaps not enough motivation for anyone to hit the go bit. There was some interest from the msm folks about a month ago, and it has been an invaluable tool on CrOS for the past ~year. Hopefully someone can dig into this and provide some feedback so we can move this forward.
Thanks!
Sean
Changes since last v6: -Rebased on drm-tip
Original v6 of the set available here: https://patchwork.freedesktop.org/series/78133/ https://lore.kernel.org/dri-devel/20200818210510.49730-1-sean@poorly.run/
Woo! Yes!
Do you have a link to your userspace?
Hi Pekka, Probably less interesting that you're hoping for, but here are the CrOS patches to enable and collect tracing:
https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2354674 https://chromium-review.googlesource.com/c/chromiumos/platform/crosutils/+/2...
You wouldn't happen to have already written a privileged userspace service that would deliver on request the logs to non-privileged actors like a compositor to be dumped in an error report?
Our feedback report generation (log_tool.cc above) collects the logs (depending on user log preferences) from across the system and packages them up for submission when requested by the user. For drm_trace, we grab them from debugfs since we don't have tracefs mounted.
You could adapt this code to change the delivery method, but I'm not sure how much value it would add beyond writing your own purpose-built service.
Indeed. Thanks anyway! :-) pq