[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 04/18] xen/arm: While a domain is suspended put its watchdogs on pause

On Mon, 2018-11-12 at 15:33 +0000, Andrew Cooper wrote:
> On 12/11/18 15:31, Mirela Simonovic wrote:
> > 
> > Thanks, now it's clear. We need to change the type for
> > watchdog_timer
> > to be the derived structure of timer that additionally contains
> > 'suspended' variable. That makes sense, we'll do so.
> Why do you need a suspended variable?  Stash the frequency the guest
> requested on the last hypercall, and fully kill/re-create the timer
> on
> suspend/resume.
I *think* what they want is something like: when, at time t1, a domain
is suspended, it has a (watchdog) timer armed, which was going to
expire and fire in 13.2 ms (i.e., at t1 + 13.2ms); when, at time t2 >>
t1, the domain is resumed, that (watchdog) timer should fire in 13.2
ms, i.e. at t2 + 13.2ms.

This being said, I don't see a behavior like this terribly useful for a
whatchdog either (but I may be missing something).

<<This happens because I choose it to happen!>> (Raistlin Majere)
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

Attachment: signature.asc
Description: This is a digitally signed message part

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.