From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Fri, 06 Jul 2012 01:18:25 +0000 Subject: Re: [PATCH 3/4] Watchdog exit handling support Message-Id: <4FF63CE1.301@freescale.com> List-Id: References: <1340861999-31281-3-git-send-email-Bharat.Bhushan@freescale.com> In-Reply-To: <1340861999-31281-3-git-send-email-Bharat.Bhushan@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ppc@vger.kernel.org On 07/05/2012 08:16 PM, Bhushan Bharat-R65777 wrote: > > >> -----Original Message----- >> From: Wood Scott-B07421 >> Sent: Friday, July 06, 2012 6:30 AM >> To: Bhushan Bharat-R65777 >> Cc: Wood Scott-B07421; qemu-ppc@nongnu.org; kvm-ppc@vger.kernel.org; >> agraf@suse.de >> Subject: Re: [PATCH 3/4] Watchdog exit handling support >> >> On 07/05/2012 07:43 PM, Bhushan Bharat-R65777 wrote: >>> Your initial comment was "We should probably call this function before >>> returning to KVM". Which suggest that ioctls calls made by QEMU to >>> enter KVM. I am a bit confused, now you want to avoid long delays in >>> QEMU? This suggest whenever we exit to qemu, right? >> >> Whenever we exit to QEMU is one possibility, though it's probably too aggressive >> (if the guest gets stuck in a loop that contains a QEMU exit, the watchdog won't >> catch it). Another option is to reset the state machine only when the guest >> resumes from a debug halt. > > Ok. > > Resetting the state machine does not disable watchdog, it will just > ensure the longest time for debug halt etc. Is that ok ? I'm talking about TSR, not TCR. It's not about disabling the watchdog or changing the period, but clearing any event that has happened when leaving debug halt. -Scott