From: Lei Yu <yulei.sh@bytedance.com>
To: Alexander Amelkin <a.amelkin@yadro.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: adding sync method in phosphor-time-manager
Date: Fri, 9 Apr 2021 15:26:24 +0800 [thread overview]
Message-ID: <CAGm54UE8q10dx6Q2KCFMSXv4MpVLQJ7njOHbwMD1dWMtSMr3Vw@mail.gmail.com> (raw)
In-Reply-To: <80ea13b3-1779-b2b3-c295-3d09dfd41987@yadro.com>
On Fri, Apr 9, 2021 at 2:17 AM Alexander Amelkin <a.amelkin@yadro.com> wrote:
>
> Hi Patrick, everybody!
>
> As far as I can see, this discussion has had no development, to our regret.
> We would really like to read some clarification on what is the proposed
> method
> of timekeeping for x86 systems nowadays, because with TimeOwner interface
> removed, it's not clear to me anymore.
>
> Do you allow the users to set time/date on the BMC side? If so, how do you
> propagate those changes on to the host, which in x86 is the owner of RTC?
> What if the BMC is rebooted before the time settings are propagated?
>
> If you don't allow setting the time in BMC, then what are the options
> for the user?
> Do you allow a choice between NTP and Host time only?
>
> How and when is the time synced from the host? Is there a method to
> force a sync?
In our x86 system, what we do is:
1. Sync time during BMC boot from ME;
2. Use NTP in BMC side and never sync time from host (ME) anymore.
3. Ignore time settings from host if there is any.
--
BRs,
Lei YU
prev parent reply other threads:[~2021-04-09 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 17:38 adding sync method in phosphor-time-manager Velumani T-ERS,HCLTech
2020-10-06 21:41 ` Richard Hanley
2020-10-07 1:38 ` Patrick Williams
2020-10-07 17:18 ` Velumani T-ERS,HCLTech
2020-10-07 1:34 ` Patrick Williams
2021-04-08 18:08 ` Alexander Amelkin
2021-04-08 19:36 ` Ed Tanous
2021-04-09 7:26 ` Lei Yu [this message]
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=CAGm54UE8q10dx6Q2KCFMSXv4MpVLQJ7njOHbwMD1dWMtSMr3Vw@mail.gmail.com \
--to=yulei.sh@bytedance.com \
--cc=a.amelkin@yadro.com \
--cc=openbmc@lists.ozlabs.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).