From: Jan Beulich <jbeulich@suse.com>
To: Andreas Kinzler <hfp@posteo.de>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] wall clock drift on Coffee Lake / C24x mainboard (HPET broken?), best practices
Date: Tue, 19 Nov 2019 10:29:51 +0100 [thread overview]
Message-ID: <db8d7ae7-3abd-6df6-cd14-6dee3619e4be@suse.com> (raw)
In-Reply-To: <5991e76e-f4bd-971f-110e-d87fbc19a437@posteo.de>
On 18.11.2019 20:35, Andreas Kinzler wrote:
> On 15.11.2019 12:01, Andreas Kinzler wrote:
>> On 14.11.2019 12:29, Jan Beulich wrote:
>>> On 14.11.2019 00:10, Andreas Kinzler wrote:
>>>> I came across the following: https://lkml.org/lkml/2019/8/29/536
>>>> Could that be the reason for the problem mentioned below? Xen is using
>>>> HPET as clocksource on the platform/mainboard. Is there an (easy) way to
>>>> verify if Xen uses PC10?
>>> Hence I can only suggest that you try again with limited or no
>>> use of C states, to at least get a hint as to a possible
>> I changed the BIOS setting to a limit of PC7 and it is now running. I
>> have to wait for the result. Thanks.
>
> Previously the drift after 4 days uptime was 60 sec. Now after 4 days
> uptime drift is 9 sec. So setting the package c-state limit to PC7 was a
> success.
9s still seems quite a lot to me, but yes, it's an improvement.
Now would you be up to checking whether, rather than via BIOS
settings (which not all BIOSes may offer) the same can be
achieved by using Xen's command line option "max_cstate="?
Also did you check whether further limiting C state use would
further improve the situation? And did you possibly also check
whether telling Xen not to use the HPET would make a difference?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-19 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 18:47 [Xen-devel] wall clock drift on C24x mainboard, best practices Andreas Kinzler
2019-11-13 23:10 ` [Xen-devel] wall clock drift on Coffee Lake / C24x mainboard (HPET broken?), " Andreas Kinzler
2019-11-14 11:29 ` Jan Beulich
2019-11-15 11:01 ` Andreas Kinzler
2019-11-18 19:35 ` Andreas Kinzler
2019-11-19 9:29 ` Jan Beulich [this message]
2019-11-19 14:31 ` Andreas Kinzler
2019-11-19 14:44 ` Jan Beulich
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=db8d7ae7-3abd-6df6-cd14-6dee3619e4be@suse.com \
--to=jbeulich@suse.com \
--cc=hfp@posteo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).