ftrace: Fix not to write duplicate header when append to existing ftrace file #411
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, tee-supplicant appends to an existing prof file if OP-TEE provides a non-zero id in the rpc call parameter. However, for ftrace data, there is always a header in the buffer.
This patch makes tee-supplicant not to write duplicate header by locating the ftrace magic and discarding data before it when tee-supplicant receives a non-zero ftrace id.
This is required for OP-TEE/optee_os#7657 to produce correct ftrace data.