From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/3] Fix overflow when applying tsc2nsec calculations
Date: Fri, 16 Apr 2021 13:34:06 +0300 [thread overview]
Message-ID: <20210416103409.24597-1-tz.stoyanov@gmail.com> (raw)
Verify that applying tsc2nsec corrections on the recorded timestamps will not
cause an overflow. When recording the trace, in case of tsc2nsec clock, get
the first TSC timestamp as offset to be used in tsc2nsec conversion.
v2 changes:
- Optimize the logic for getting the timestamp of the first recorded event.
Tzvetomir Stoyanov (VMware) (3):
trace-cmd library: Add new trace-cmd library APIs for guest ts
corrections
trace-cmd library: Add check before applying tsc2nsec offset
trace-cmd: Get the timestamp of the first recorded event as TSC offset
.../include/private/trace-cmd-private.h | 18 ++-
lib/trace-cmd/trace-input.c | 116 ++-----------
lib/trace-cmd/trace-timesync.c | 113 ++++++++++---
tracecmd/include/trace-local.h | 1 +
tracecmd/trace-record.c | 152 ++++++++++++++----
5 files changed, 246 insertions(+), 154 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-16 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 10:34 Tzvetomir Stoyanov (VMware) [this message]
2021-04-16 10:34 ` [PATCH v2 1/3] trace-cmd library: Add new trace-cmd library APIs for guest ts corrections Tzvetomir Stoyanov (VMware)
2021-04-16 10:34 ` [PATCH v2 2/3] trace-cmd library: Add check before applying tsc2nsec offset Tzvetomir Stoyanov (VMware)
2021-04-16 20:12 ` Steven Rostedt
2021-04-19 8:08 ` Tzvetomir Stoyanov
2021-04-19 13:45 ` Steven Rostedt
2021-04-19 15:14 ` Steven Rostedt
2021-04-28 12:31 ` Tzvetomir Stoyanov
2021-04-16 10:34 ` [PATCH v2 3/3] trace-cmd: Get the timestamp of the first recorded event as TSC offset Tzvetomir Stoyanov (VMware)
2021-04-16 19:28 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210416103409.24597-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.