-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drm/atomic: Better logging for atomic requests #1635
Conversation
234293c
to
3616765
Compare
3616765
to
1ede934
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No idea why we had &dyn Iterator
here, but imo this is the perfect opportunity to get rid of it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EDIT: wrong text input...
Co-authored-by: Christian Meissl <[email protected]>
6da1b06
to
5ed3394
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Invalid screen configuration
issues are rare these days, but decrypting them from logs is very cumbersome whenever they occur. This is mostly due to the property handles not having any meaning, if you don't have the property mapping.So we do log the mapping now as well.
Additionally in debug mode we construct the whole request differently to give us actually nice output. We need a bunch of collections to do so, so this is inefficient enough to only do in debug builds, long term it might be better to find a solution how to deconstruct drm-rs's
AtomicModeReq
. But for now this should be a significant improvement.