commit 0afe9fced177ae49b7f25dff819b2551a1fb13fc
author Harkiran Bolaria <hbolaria@google.com> Fri Dec 16 16:34:39 2022
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Fri Dec 16 16:34:39 2022
tree c9aa70c24a7af1e6e1a9cd00a988e6e457d032a2
parent 1ac433033dfc7a9a7ecb628a16156cec4ca13ed9

Record input events/flows for long-task input/browser interval calculations.

In order to calculate chrome input to browser intervals, needed for
tracking chrome long tasks blocking input, we need to know the
duration between input queuing time and latencyInfo, including what
type of input. This patch ensures that long task tracking will
produce the minimum information needed to calculate these intervals
as they are currently being calculated, including queue time, flow,
IPC, and ensuring that the latencyInfo is associated with the
correct IPC.

Input type comes from an IPC, which won't be known at queueing time. Further, delaying the recording to the time IPC is known results in
incorrect timestamp processing in TRACE_EVENT_INSTANT, resulting in
incorrect interval calculations.

Change-Id: I405e989fcdbfa027662268b4687b643704d674fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4071005
Reviewed-by: Kyle Charbonneau <kylechar@chromium.org>
Reviewed-by: Stephen Nusko <nuskos@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Harkiran Bolaria <hbolaria@google.com>
Cr-Commit-Position: refs/heads/main@{#1084349}