From: 'Yi Sun' <yi.sun@intel.com>
To: David Laight <David.Laight@aculab.com>
Cc: "dave.hansen@intel.com" <dave.hansen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"sohil.mehta@intel.com" <sohil.mehta@intel.com>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"heng.su@intel.com" <heng.su@intel.com>
Subject: Re: [PATCH 1/2] x86/fpu: Measure the Latency of XSAVE and XRSTOR
Date: Tue, 26 Jul 2022 17:03:55 +0800 [thread overview]
Message-ID: <Yt+t+zlen1xHXhS1@ysun46-mobl1> (raw)
In-Reply-To: <921078bc2a994d3ab6aba26d4654cb47@AcuMS.aculab.com>
On 24.07.2022 20:54, David Laight wrote:
>From: Yi Sun
>> Sent: 23 July 2022 09:38
>>
>> Calculate the latency of instructions xsave and xrstor with new trace
>> points x86_fpu_latency_xsave and x86_fpu_latency_xrstor.
>>
>> The delta TSC can be calculated within a single trace event. Another
>> option considered was to have 2 separated trace events marking the
>> start and finish of the xsave/xrstor instructions. The delta TSC was
>> calculated from the 2 trace points in user space, but there was
>> significant overhead added by the trace function itself.
>>
>> In internal testing, the single trace point option which is
>> implemented here proved to be more accurate.
>...
>
>I've done some experiments that measure short instruction latencies.
>Basically I found:
>1) You need a suitable serialising instruction before and after
> the code being tested - otherwise it can overlap whatever
> you are using for timing.
The original comments here are kindly not so exact. The patch actually
makes use of trace_clock to calculate the latency but not TSC directly.
The precision here is "at most ~1 jiffy between CPUs" which is probably
acceptable to this usage.
I would like refine the comments if it made confusing.
Thanks
--Sun, Yi
next prev parent reply other threads:[~2022-07-26 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 8:37 [PATCH 0/2] x86: Add xsave/xrstor Latency Trace Events and Consuming Script Yi Sun
2022-07-23 8:37 ` [PATCH 1/2] x86/fpu: Measure the Latency of XSAVE and XRSTOR Yi Sun
2022-07-24 20:54 ` David Laight
2022-07-24 23:00 ` Luck, Tony
2022-07-25 7:35 ` David Laight
2022-07-25 17:44 ` Dave Hansen
2022-07-26 7:41 ` David Laight
2022-07-26 9:03 ` 'Yi Sun' [this message]
2022-07-28 18:46 ` Sohil Mehta
2022-07-23 8:38 ` [PATCH 2/2] scripts/x86: 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=Yt+t+zlen1xHXhS1@ysun46-mobl1 \
--to=yi.sun@intel.com \
--cc=David.Laight@aculab.com \
--cc=dave.hansen@intel.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
all inboxes | Powered by JetHome®