openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tu <wltu@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc: "Bills, Jason M" <jason.m.bills@linux.intel.com>,
	Charles.Hsu@quantatw.com, William Kennington <wak@google.com>
Subject: Re: [phosphor-sel-logger] Watchdog Event Monitor Usage
Date: Tue, 10 Aug 2021 21:55:06 -0700	[thread overview]
Message-ID: <CAHwn2X=gfL7h54JqR8xF3X2eQnK3JkFqDGLB+rLEH94c6mvspA@mail.gmail.com> (raw)
In-Reply-To: <CAHwn2X=uDqvQiH05+zSpZiuF-t6iHYpucXXSLDJjn4TfZ0iOUA@mail.gmail.com>

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

Just a friendly ping on this topic.

If no one has any concern, then I will replace it.

Adding `Charles.Hsu@quantatw.com` since he added this feature.

On Mon, Aug 9, 2021 at 1:38 PM Willy Tu <wltu@google.com> wrote:

> Hi all,
>
> I am writing this to see if anyone is using the Watchdog Event Monitor
> option in phosphor-sel-logger.
>
> Option: `log-watchdog`
>
> I have made a few changes to `phosphor-watchdog` that sends out Timeout
> signals during timeout events.
>
> See https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-watchdog/+/44749
>
> I am thinking of replacing the existing watchdog event to check that
> signal instead or checking for the `Enabled` property change.
>
> See
> https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-sel-logger/+/45622
>
> I think the existing change is wrong, since changing the `Enabled`
> property does not necessary mean the watchdog event got triggered.
>
> So I am wondering if anyone needs the watchdog event monitor? or if I can
> replace it.
>
> Best,
>
> Willy Tu
>

[-- Attachment #2: Type: text/html, Size: 1829 bytes --]

      reply	other threads:[~2021-08-11  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 20:38 [phosphor-sel-logger] Watchdog Event Monitor Usage Willy Tu
2021-08-11  4:55 ` Willy Tu [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='CAHwn2X=gfL7h54JqR8xF3X2eQnK3JkFqDGLB+rLEH94c6mvspA@mail.gmail.com' \
    --to=wltu@google.com \
    --cc=Charles.Hsu@quantatw.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=wak@google.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 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).