From: Yi Sun <yi.sun@intel.com>
To: dave.hansen@intel.com, sohil.mehta@intel.com,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
x86@kernel.org, david.laight@aculab.com
Cc: heng.su@intel.com, yi.sun@intel.com
Subject: [PATCH v2 0/2] x86: Add xsave/xrstor Latency Trace Events and Consuming Script
Date: Fri, 29 Jul 2022 17:56:06 +0800 [thread overview]
Message-ID: <20220729095608.1475138-1-yi.sun@intel.com> (raw)
This series introduces trace events which can dump the latency of
instructions xsave and xrstor for x86 platform to tell when
XSAVE/XRSTOR are getting more or less expensive, and get out the
RFBM and XINUSE to figure out the reason.
We did bunch of internal testing, compared several optional latency
calculation approaches. We believe it can be a more optimized one.
Also, the series introduces a script to consume trace log, which
leverage sqlite3 to show statistics data such as max, min, latency
and 97% tail latency.
This series has gone through several versions of peer-reviewed
internally. All patches have review tags. It's ready for review by
the x86@kernel.org maintainers.
- Change from v1 to v2:
- Reword the comments. (Laight, David; Mehta, Sohil)
- Rename all variable 'dtsc' to 'latency'. (Mehta, Sohil)
Yi Sun (2):
x86/fpu: Measure the Latency of XSAVE and XRSTOR
scripts/x86: Add script to consume trace log of xsave latency
arch/x86/include/asm/trace/fpu.h | 35 +++++
before submission.
arch/x86/kernel/fpu/xstate.h | 49 ++++++-
scripts/x86/xsave-latency-trace.sh | 227 +++++++++++++++++++++++++++++
3 files changed, 306 insertions(+), 5 deletions(-)
create mode 100755 scripts/x86/xsave-latency-trace.sh
--
2.34.1
next reply other threads:[~2022-07-29 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 9:56 Yi Sun [this message]
2022-07-29 9:56 ` [PATCH v2 1/2] x86/fpu: Measure the Latency of XSAVE and XRSTOR Yi Sun
2022-07-29 9:56 ` [PATCH v2 2/2] scripts/x86: Add script to consume trace log of xsave latency Yi Sun
2022-08-02 11:03 ` Ingo Molnar
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=20220729095608.1475138-1-yi.sun@intel.com \
--to=yi.sun@intel.com \
--cc=dave.hansen@intel.com \
--cc=david.laight@aculab.com \
--cc=heng.su@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sohil.mehta@intel.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox