From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Bhushan Bharat-R65777 <R65777@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>,
"<bharatb.yadav@gmail.com>" <bharatb.yadav@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Kumar Gala <galak@kernel.crashing.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH 2/2 v2] KVM: PPC: booke: Add watchdog emulation
Date: Tue, 17 Jul 2012 18:00:32 +0000 [thread overview]
Message-ID: <5005A840.8070200@freescale.com> (raw)
In-Reply-To: <50059820.7050305@suse.de>
On 07/17/2012 11:51 AM, Alexander Graf wrote:
> On 07/17/2012 06:27 PM, Scott Wood wrote:
>> Determining whether we're on final expiration is based only on the
>> previous value of TSR[ENW,WIS] when the timer expires. We look at TCR
>> to determine whether we need to actually exit to QEMU (as opposed to a
>> final expiration with no action, which still should result in the timer
>> being stopped), but I don't see any problematic races there as long as
>> we don't try to update TCR from that context.
>
> Yeah, what I was trying to say is that I would like to keep the TSR
> state unmodified for the final expiry case. If user space decides to not
> act upon it, it should be able to call into VCPU_RUN and have the same
> behavior as if the watchdog never expired.
I agree, it would be racy for QEMU to have to clear TSR if it's not
doing a full reset. And that fact is making me wonder if I should have
listened to you and kept TSR owned by the vcpu thread. :-)
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Bhushan Bharat-R65777 <R65777@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>,
"<bharatb.yadav@gmail.com>" <bharatb.yadav@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Kumar Gala <galak@kernel.crashing.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH 2/2 v2] KVM: PPC: booke: Add watchdog emulation
Date: Tue, 17 Jul 2012 13:00:32 -0500 [thread overview]
Message-ID: <5005A840.8070200@freescale.com> (raw)
In-Reply-To: <50059820.7050305@suse.de>
On 07/17/2012 11:51 AM, Alexander Graf wrote:
> On 07/17/2012 06:27 PM, Scott Wood wrote:
>> Determining whether we're on final expiration is based only on the
>> previous value of TSR[ENW,WIS] when the timer expires. We look at TCR
>> to determine whether we need to actually exit to QEMU (as opposed to a
>> final expiration with no action, which still should result in the timer
>> being stopped), but I don't see any problematic races there as long as
>> we don't try to update TCR from that context.
>
> Yeah, what I was trying to say is that I would like to keep the TSR
> state unmodified for the final expiry case. If user space decides to not
> act upon it, it should be able to call into VCPU_RUN and have the same
> behavior as if the watchdog never expired.
I agree, it would be racy for QEMU to have to clear TSR if it's not
doing a full reset. And that fact is making me wonder if I should have
listened to you and kept TSR owned by the vcpu thread. :-)
-Scott
next prev parent reply other threads:[~2012-07-17 18:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 10:34 [PATCH 2/2 v2] KVM: PPC: booke: Add watchdog emulation Bharat Bhushan
2012-07-09 10:46 ` Bharat Bhushan
2012-07-16 17:18 ` Alexander Graf
2012-07-16 17:18 ` Alexander Graf
2012-07-17 1:02 ` Scott Wood
2012-07-17 1:02 ` Scott Wood
2012-07-17 7:20 ` Alexander Graf
2012-07-17 7:20 ` Alexander Graf
2012-07-17 9:57 ` Bhushan Bharat-R65777
2012-07-17 12:51 ` Alexander Graf
2012-07-17 12:51 ` Alexander Graf
2012-07-17 13:15 ` Bhushan Bharat-R65777
2012-07-17 14:01 ` Alexander Graf
2012-07-17 14:01 ` Alexander Graf
2012-07-17 14:13 ` Bhushan Bharat-R65777
2012-07-17 14:35 ` Alexander Graf
2012-07-17 14:35 ` Alexander Graf
2012-07-17 16:10 ` Bhushan Bharat-R65777
2012-07-17 16:27 ` Scott Wood
2012-07-17 16:27 ` Scott Wood
2012-07-17 16:51 ` Alexander Graf
2012-07-17 16:51 ` Alexander Graf
2012-07-17 18:00 ` Scott Wood [this message]
2012-07-17 18:00 ` Scott Wood
2012-07-17 11:31 ` Bhushan Bharat-R65777
2012-07-17 11:31 ` Bhushan Bharat-R65777
2012-07-17 16:37 ` Scott Wood
2012-07-17 16:37 ` Scott Wood
2012-07-17 16:56 ` Bhushan Bharat-R65777
2012-07-17 16:56 ` Bhushan Bharat-R65777
2012-07-17 17:00 ` Scott Wood
2012-07-17 17:00 ` Scott Wood
2012-07-17 17:10 ` Bhushan Bharat-R65777
2012-07-17 17:10 ` Bhushan Bharat-R65777
2012-07-17 17:25 ` Scott Wood
2012-07-17 17:25 ` Scott Wood
2012-07-17 17:29 ` Bhushan Bharat-R65777
2012-07-17 17:29 ` Bhushan Bharat-R65777
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=5005A840.8070200@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bharatb.yadav@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.