From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH 0/4] x86: reduce errors in frequency calculations / unrelated cleanup
Date: Fri, 13 Mar 2020 10:23:51 +0100 [thread overview]
Message-ID: <60130f14-3fc5-e40d-fec6-2448fefa6fc4@suse.com> (raw)
While looking into ways to increase the accuracy of the clock speeds
we work with (in particular by possibly obtaining information from
hardware rather than measuring), I first of all noticed some
avoidable rounding errors in some of our calculations. That's what
patches 2 and 3 are intended to deal with. Patch 1 is preparatory
cleanup, while patch 4 simply addresses something I got annoyed by
yet another time while doing this investigation.
1: APIC: adjust types and comments in calibrate_APIC_clock()
2: time: reduce rounding errors in calculations
3: APIC: reduce rounding errors in calculations
4: APIC: restrict certain messages to BSP
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2020-03-13 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 9:23 Jan Beulich [this message]
2020-03-13 9:25 ` [Xen-devel] [PATCH 1/4] x86/APIC: adjust types and comments in calibrate_APIC_clock() Jan Beulich
2020-03-13 14:46 ` Andrew Cooper
2020-03-13 9:25 ` [Xen-devel] [PATCH 2/4] x86/time: reduce rounding errors in calculations Jan Beulich
2020-03-13 15:14 ` Andrew Cooper
2020-03-16 8:58 ` Jan Beulich
2020-03-16 13:27 ` Andrew Cooper
2020-03-13 9:26 ` [Xen-devel] [PATCH 3/4] x86/APIC: " Jan Beulich
2020-03-13 15:50 ` Andrew Cooper
2020-03-16 9:07 ` Jan Beulich
2020-03-16 13:28 ` Andrew Cooper
2020-03-13 9:26 ` [Xen-devel] [PATCH 4/4] x86/APIC: restrict certain messages to BSP Jan Beulich
2020-03-13 16:18 ` Andrew Cooper
2020-03-16 9:10 ` Jan Beulich
2020-04-02 7:55 ` Ping: " Jan Beulich
2020-04-02 17:55 ` Andrew Cooper
2020-04-03 7:32 ` Jan Beulich
2020-05-14 10:01 ` Roger Pau Monné
2020-05-14 12:31 ` Jan Beulich
2020-05-14 13:12 ` 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=60130f14-3fc5-e40d-fec6-2448fefa6fc4@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.