v6:
---
1. Create a new option "--timestamp-boundary" in perf record.
Currently '--buildid-all' is not enabled by default. So the walking
on all samples is the default operation. There is no big overhead
to calculate the timestamp boundary in process_sample_event handler
once we already go through all samples. So the timestamp boundary
calculation is enabled by default when '--buildid-all' is not enabled.
While if '--buildid-all' is enabled, we creates a new option
"--timestamp-boundary" for user to decide if it enables the
timestamp boundary calculation.
Impacted patch:
---------------
perf record: Get the first sample time and last sample time
2. Fix the merge issue with the latest perf/core branch.
No functional changes.
Impacted patch:
---------------
perf report: support time percent and multiple time ranges
perf script: support time percent and multiple time ranges