This is a small improvement idea I had while I was working on the UI change. I'll wait for the prerequisite Perfetto PR (which modifies the protos) to land before merging this, but would you mind taking a look in the meantime? Thanks! : )
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
LGTM, thanks!
packet_data, opcode)) {Nit: we don't quite need to plumb opcode here because `header` is also passed, which contains EventDescriptor.Opcode.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Would you mind taking another look? The CR+1 was removed since the set of files changed. Thanks again!
Nit: we don't quite need to plumb opcode here because `header` is also passed, which contains EventDescriptor.Opcode.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
tracing: pass file I/O opcodes to Perfetto
This change passes an opcode field to Perfetto for file I/O events that
correspond to multiple opcodes.
Some file I/O ETW events correspond to multiple types (each with their
own opcode). For example, the FileIo_ReadWrite event can have opcode 67
(file read) or 68 (file write) [1]. Both have the same structure.
Knowing the opcode at the time of parsing will enable Perfetto to be
most descriptive (e.g., distinguishing reads from writes).
The full list of opcodes is here:
https://learn.microsoft.com/en-us/windows/win32/etw/fileio
The Perfetto change to add opcode to these protos is here:
https://github.com/google/perfetto/pull/4086
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |