RFC Add timestamp to process event connector message
Get series with b4
b4 am 1133845225.25202.1373.camel@starkVersions newest first
- v1 RFC Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Add getnstimestamp functioninclude/ kernel/ | +23 | 0 replies | |
| 2/2 | Add timestamp field to process eventsdrivers/ include/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 000/002] Add timestamp to process event connector message
This series of patches adds a timestamp field to the events sent
via the process event connector. The timestamp allows listeners to accurately account the duration(s) between a process' events and offers strong means with which to determine the order of events while also avoiding the addition of per-task data.
Series:
getnstimestamp.patch
proc-events-timestamp.patch
The first patch adds a new generic function, getnstimestamp(),
which gets an SMP-safe high-resolution monotonic timestamp.
The second patch adds a timestamp field to the events sent via
the process event connector and fills the field using the new timestamp function. It alters the size and layout of the event structure and hence would break compatibility if not incorporated with the first release of process events connector in a mainline kernel.
Cheers,
-Matt Helsley