Skip to content

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

Merged
lgirdwood merged 1 commit into
thesofproject:masterfrom
RanderWang:master
Jul 2, 2018
Merged

lgirdwood merged 1 commit into
thesofproject:masterfrom
RanderWang:master

Conversation

@RanderWang

Copy link
Copy Markdown
Collaborator

Refine dtrace_event_atomic according to dtrace_event

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

@lgirdwood lgirdwood left a comment

Copy link
Copy Markdown
Member

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.

Comment thread src/lib/dma-trace.c Outdated

Copy link
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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
Copy Markdown
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.

3 participants