Skip to content
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

DMA-Trace: fix dma-trace overflow issue #23

Merged
merged 1 commit into from Jul 2, 2018

Conversation

RanderWang
Copy link
Collaborator

Refine dtrace_event_atomic according to dtrace_event

Signed-off-by: Rander Wang rander.wang@linux.intel.com

Copy link
Member

@lgirdwood lgirdwood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message needs description of what is done and why.

Please also include the issue number/link, otherwise we cant track.

@@ -391,9 +391,29 @@ void dtrace_event(const char *e, uint32_t length)

void dtrace_event_atomic(const char *e, uint32_t length)
{
struct dma_trace_buf *buffer = NULL;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks exactly like dtrace_event() now without the locking. The purpose of the atomic call is for low frequency and fast trace messages. If we are overflowing then the atomic user is sending too many trace messages and should be converted to verbose_trace

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

linked to #17

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it should be convert to verbose_trace.

Refine trace log in pm module. There are too many
put|get events, so use verbose trace. And atomic
trace is for low frequency and fast trace messages

Signed-off-by: Rander Wang <rander.wang@linux.intel.com>
@xiulipan
Copy link
Contributor

This patch look good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants