From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Tim Deegan" <tim@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wei.liu2@citrix.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xen.org, "Julien Grall" <julien.grall@arm.com>
Subject: Re: [PATCH v5] new config option vtsc_tolerance_khz to avoid TSC emulation
Date: Thu, 29 Mar 2018 11:23:21 +0200 [thread overview]
Message-ID: <20180329092321.GJ30726@aepfle.de> (raw)
In-Reply-To: <5ABCC17902000078001B709B@prv1-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 319 bytes --]
On Thu, Mar 29, Jan Beulich wrote:
> When you use abs() or alike in places like this, it is more immediately
> obvious to the reader what you're doing.
Does every supported compiler actually understand this?
int khz_diff = __builtin_abs(cpu_khz - gtsc_khz);
Or do we need an inline abs() in case it is not gcc?
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-29 9:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 9:26 [PATCH v5] new config option vtsc_tolerance_khz to avoid TSC emulation Olaf Hering
2018-03-28 16:27 ` Wei Liu
2018-03-28 16:49 ` George Dunlap
2018-03-28 16:52 ` Wei Liu
2018-03-28 17:07 ` George Dunlap
2018-03-28 17:13 ` Wei Liu
2018-03-29 8:04 ` Jan Beulich
2018-03-29 8:17 ` Olaf Hering
2018-03-29 8:35 ` Jan Beulich
2018-03-29 9:23 ` Olaf Hering [this message]
2018-03-29 9:56 ` Jan Beulich
2018-03-29 10:05 ` Olaf Hering
2018-03-29 10:36 ` Jan Beulich
2018-03-29 8:25 ` Roger Pau Monné
2018-03-29 8:32 ` Olaf Hering
2018-03-29 8:53 ` Jan Beulich
2018-03-29 8:58 ` Olaf Hering
2018-03-29 9:06 ` Roger Pau Monné
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=20180329092321.GJ30726@aepfle.de \
--to=olaf@aepfle.de \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.