Ignore unexpected warnings in PerfDataSampleReader::Append
#201
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.
probem
Recently, commit
623c777upgraded perf_data_converter. There are some changes in thePerfParser::MapBranchStack. In the new version, even if the mapping of from_ip fails, the mapping process forto_ipwill still proceed. This may lead to a situation wherefrom.offset_equals the initial value 0 whenfrom_ipmapping fails, andto.offset_equals the actual offset whento_ipmapping succeeds. In addition, in my test, these unmatched IPs are very large kernel stack addresses such as0xffffffffa9400ac7. This inconsistency may cause the subsequent check to erroneously warn about "Bogus LBR data". A large number of such warnings during use are more likely to cause confusion and need to be filtered in advance.Here is my solution. If from does not match, continue in advance, probably not the best solution.
test case output
test case