| Re: [chrony-dev] timex kernel offset parameter not updated |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] timex kernel offset parameter not updated
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 12 Mar 2024 10:02:28 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710234149; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fvYNAukAnaBbtXMaABoYmiL4YjvZnyWwbFnj2R/1h7I=; b=QtwQcZqRO0wezCH6x8Pb49rad/6djqK+PHrSE1eya4kaFjvzvIKxzwnU+9hEZAPrfaTszM tEE9xIMzeJLwscGwTc7h78hkP5M6Nk8dcgTEs+6rfGCe2aN9z9ahXpLpmjsnpDzF7xsLZi z+3CU1KKmLQYOkKbev4ymbcbrgaE91E=
On Tue, Mar 12, 2024 at 08:35:43AM +0000, Filip Verwee wrote:
> Hi Miroslav,
>
> Thanks for the reply.
>
> Even if chronyd is not using the kernel PLL, wouldn't it be still possible to update the offset parameter?
No, the offset can be set only when the PLL is enabled. In the
kernel code (kernel/time/ntp.c):
static void ntp_update_offset(long offset)
{
s64 freq_adj;
s64 offset64;
long secs;
if (!(time_status & STA_PLL))
return;
Even if it could be set and it did nothing except being reported back
in timex, chronyd would need to update it periodically to be useful.
I don't think that would be acceptable as chronyd is supposed to be
friendly to power saving.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.