From: Yi Sun <yi.sun@intel.com>
To: dave.hansen@intel.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: sohil.mehta@intel.com, ak@linux.intel.com,
ilpo.jarvinen@linux.intel.com, heng.su@intel.com,
tony.luck@intel.com, dave.hansen@linux.intel.com,
Yi Sun <yi.sun@intel.com>
Subject: [RESEND PATCH v5 0/2] x86: Add xsave/xrstor Latency Trace Events and Consuming Script
Date: Tue, 25 Oct 2022 20:17:47 +0800 [thread overview]
Message-ID: <20221025121749.584519-1-yi.sun@intel.com> (raw)
This series introduces trace events that can leak the latency of xsave and
xrstor instructions for the x86 platform to tell when XSAVE/XRSTOR are becoming
more or less expensive, and get the RFBM and XINUSE to figure out why.
We conducted extensive internal testing and compared several latency computation
methodologies. We believe it could be improved. Also included in the series is
a script for consuming trace logs that uses sqlite3 to display statistics data
such as max, min, latency, and 97% tail latency.
- Change from v4 to v5:
- Rebase patch to the most recent tag v6.1-rc2, no conflict.
- Change from v3 to v4:
- Rebase patch set to the latest tag v6.0-rc3, replacing
ALTERNATIVE_2 with ALTERNATIVE_3
- Change from v2 to v3:
- Move the script xsave-latency-trace.sh to folder tools/testing/fpu/
(Ingo Molnar)
- 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
tools/testing/fpu: Add script to consume trace log of xsave latency
arch/x86/include/asm/trace/fpu.h | 35 ++++
arch/x86/kernel/fpu/xstate.h | 49 ++++-
tools/testing/fpu/xsave-latency-trace.sh | 227 +++++++++++++++++++++++
3 files changed, 306 insertions(+), 5 deletions(-)
create mode 100755 tools/testing/fpu/xsave-latency-trace.sh
--
2.34.1
next reply other threads:[~2022-10-25 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 12:17 Yi Sun [this message]
2022-10-25 12:17 ` [RESEND PATCH v5 1/2] x86/fpu: Measure the Latency of XSAVE and XRSTOR Yi Sun
2022-10-25 12:17 ` [RESEND PATCH v5 2/2] tools/testing/fpu: Add script to consume trace log of xsave latency Yi Sun
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=20221025121749.584519-1-yi.sun@intel.com \
--to=yi.sun@intel.com \
--cc=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=heng.su@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®