All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: vishwa <vishwa@linux.vnet.ibm.com>
Cc: Mine <mine260309@gmail.com>, OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: RFC: new design of phosphor-time-manager on sdbusplus
Date: Fri, 20 Jan 2017 13:20:59 -0600	[thread overview]
Message-ID: <20170120192059.GD5120@heinlein.lan> (raw)
In-Reply-To: <b5a30dfb-8b32-ef9d-f928-a6def24e21f1@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Thu, Jan 19, 2017 at 05:54:02PM +0530, vishwa wrote:
 
> I thought and partially agree to their concern. For changing the owner 
> *away from SPLIT*, we can actually consume that readily. Its only the 
> change * TO SPLIT* that needs to delayed until off.

Actually the opposite.  You can safely switch to split while running,
but switch from split or host needs to be deferred.

> >      2. If the process restarts we need it to go back into the "current
> >         state" and not the "requested state".  How do we make this
> >         happen?  The current implementation might also have a flaw here
> >         so maybe we log it as an issue for follow up.
> 
> 
> The current implementation only sets the values based on what was set 
> prior to reset.
> It does that by consuming the saved data in /var/lib/obmc/saved_*. So 
> there is not an issue there.

Sounds good.

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2017-01-20 19:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  7:42 RFC: new design of phosphor-time-manager on sdbusplus Mine
2017-01-13  9:11 ` Deepak Kodihalli
2017-01-13 12:35   ` Mine
2017-01-16 19:44 ` Patrick Williams
2017-01-17  7:51   ` Mine
2017-01-18 11:07     ` vishwa
2017-01-18 13:45       ` Mine
2017-01-18 14:44     ` Patrick Williams
2017-01-19  3:48       ` Mine
2017-01-19  6:11         ` vishwa
2017-01-19  7:37           ` Mine
2017-01-19  8:39             ` vishwa
2017-01-19  9:48               ` Mine
2017-01-20 19:18                 ` Patrick Williams
2017-01-20 19:08             ` Patrick Williams
2017-01-21  9:56               ` Mine
2017-01-19 12:24       ` vishwa
2017-01-20 19:20         ` Patrick Williams [this message]
2017-01-19 12:24       ` vishwa

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=20170120192059.GD5120@heinlein.lan \
    --to=patrick@stwcx.xyz \
    --cc=mine260309@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=vishwa@linux.vnet.ibm.com \
    /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.