From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Bharat Bhushan <r65777@freescale.com>,
kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>,
Bharat Bhushan <Bharat.Bhushan@freescale.com>
Subject: Re: [PATCH 2/2 v6] KVM: PPC: booke: Add watchdog emulation
Date: Wed, 01 Aug 2012 02:13:14 +0000 [thread overview]
Message-ID: <501890BA.5080009@freescale.com> (raw)
In-Reply-To: <81C75D75-BC6E-4708-8189-274D4DC1E239@suse.de>
On 07/31/2012 06:59 PM, Alexander Graf wrote:
> Well, user space always comes in via the ioctl path, which in turn
> does vcpu_load(vcpu), thus should always be running as the vcpu
> context itself.
Right, it's the timers you're racing with.
> It boils down to the original thing I was saying back when you
> introduced asynchronous TSR updates.
Right.
> Why don't we just make TSR
> updates kvm requests?
Maybe we should.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Bharat Bhushan <r65777@freescale.com>, <kvm-ppc@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>,
Bharat Bhushan <Bharat.Bhushan@freescale.com>
Subject: Re: [PATCH 2/2 v6] KVM: PPC: booke: Add watchdog emulation
Date: Tue, 31 Jul 2012 21:13:14 -0500 [thread overview]
Message-ID: <501890BA.5080009@freescale.com> (raw)
In-Reply-To: <81C75D75-BC6E-4708-8189-274D4DC1E239@suse.de>
On 07/31/2012 06:59 PM, Alexander Graf wrote:
> Well, user space always comes in via the ioctl path, which in turn
> does vcpu_load(vcpu), thus should always be running as the vcpu
> context itself.
Right, it's the timers you're racing with.
> It boils down to the original thing I was saying back when you
> introduced asynchronous TSR updates.
Right.
> Why don't we just make TSR
> updates kvm requests?
Maybe we should.
-Scott
next prev parent reply other threads:[~2012-08-01 2:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 3:49 [PATCH 2/2 v6] KVM: PPC: booke: Add watchdog emulation Bharat Bhushan
2012-07-25 3:52 ` Bharat Bhushan
2012-07-31 11:50 ` Alexander Graf
2012-07-31 11:50 ` Alexander Graf
2012-07-31 21:24 ` Scott Wood
2012-07-31 21:24 ` Scott Wood
2012-07-31 23:59 ` Alexander Graf
2012-07-31 23:59 ` Alexander Graf
2012-08-01 2:13 ` Scott Wood [this message]
2012-08-01 2:13 ` Scott Wood
2012-08-01 2:37 ` Alexander Graf
2012-08-01 2:37 ` Alexander Graf
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=501890BA.5080009@freescale.com \
--to=scottwood@freescale.com \
--cc=Bharat.Bhushan@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=r65777@freescale.com \
/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.