From: Scott Wood <scottwood@freescale.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 3/4] Watchdog exit handling support
Date: Fri, 06 Jul 2012 01:18:25 +0000 [thread overview]
Message-ID: <4FF63CE1.301@freescale.com> (raw)
In-Reply-To: <1340861999-31281-3-git-send-email-Bharat.Bhushan@freescale.com>
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
prev parent reply other threads:[~2012-07-06 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 5:51 [PATCH 3/4] Watchdog exit handling support Bharat Bhushan
2012-06-28 22:26 ` Scott Wood
2012-07-04 11:13 ` Bhushan Bharat-R65777
2012-07-05 20:27 ` Scott Wood
2012-07-06 0:43 ` Bhushan Bharat-R65777
2012-07-06 1:00 ` Scott Wood
2012-07-06 1:16 ` Bhushan Bharat-R65777
2012-07-06 1:18 ` Scott Wood [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=4FF63CE1.301@freescale.com \
--to=scottwood@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
/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