| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
It's common for services to want to pet the watchdog by reading the
interval, writing it to the TimeRemaining field, and possibly enabling
the watchdog. This patch adds a convenience method to acomplish this in
a single dbus call. A single call also reduces the completion time of
reset requests and the load incurred by performing multiple dbus calls.
Change-Id: I847e821a4ea10e49c6b6703a48a346bbab6fd44c
Signed-off-by: William A. Kennington III <wak@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The IPMI spec defines actions which can be set at runtime that define
what action the watchdog will take when it expires. With this change our
watchdog daemon can be dynamically reconfigured to execute a target that
maps to the defined action.
The current list of actions maps directly from the IPMI spec. We don't
require that the list strictly adheres to the list in the spec, but this
is a good starting point since they are generic host actions. A commit
to phosphor-watchog will accompany this change in order to respect the
actions defined in this interface. This change defaults the action to
HardReset, which will ensure the behavior is consistent with previous
behavior regardless of updating the phosphor-host-ipmid.
Change-Id: I7b293394326652b292b4bd23950a7f947ece8306
Signed-off-by: William A. Kennington III <wak@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding an initialization value to the dbus api allows the host ipmi
daemon or any other user of the host watchdog api to determine if they
have already initialized the host watchdog without keeping any of their
own state. This is useful for being able to report a not initialized error
to the host system when it makes a watchdog reset call. Since this value
is defined by default as false, whenever the watchdog daemon restarts
and loses state the host will be able to see that it has not yet been
initialized. The host can then reinitialize the watchdog if implemented
according to the spec. As this value is inteded purely for state tracking
on the client side, the server does not need to modify or even read this value.
Change-Id: I224995fdb09fcf21ba729dbd88e41a31e82eacad
Signed-off-by: William A. Kennington III <wak@google.com>
|
| |
|
|
|
| |
Change-Id: I0e67d6b6a476ac6212d53fbdfd7efc3e9c06f7ab
Signed-off-by: Patrick Venture <venture@google.com>
|
| |
|
|
|
|
|
|
|
|
| |
Initial thought behind watchdog implementation was that when
the timer expires, it would broadcast a signal. A better design
was thought of in the meantime and that would call into a
user requested target post timer expiration.
Change-Id: Ibe148ed5cd0e8d72949324f64c87704a8e9e7236
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
Add a generic interface for watchdog, for system state monitoring.
Partially resolves: openbmc/openbmc#767
Change-Id: I7f04fe9e8a35669612501b05a1a06e03e9928194
Signed-off-by: Yi Li <adamliyi@msn.com>
|
