From: Izik Eidus <izike@qumranet.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: "Dong, Eddie" <eddie.dong@intel.com>,
kvm-devel@lists.sourceforge.net, jeremy@goop.org,
linux-kernel@vger.kernel.org, hollisb@us.ibm.com,
avi@qumranet.com
Subject: Re: [kvm-devel] [PATCH 2/3] kvmclock - the host part.
Date: Tue, 13 Nov 2007 14:08:19 +0200 [thread overview]
Message-ID: <473993B3.4060508@qumranet.com> (raw)
In-Reply-To: <4739906B.2080103@redhat.com>
Glauber de Oliveira Costa wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dong, Eddie escreveu:
>
>>> +static void kvm_write_guest_time(struct kvm_vcpu *vcpu) +{
>>> + struct timespec ts;
>>> + int r;
>>> +
>>> + if (!vcpu->clock_gpa)
>>> + return;
>>> +
>>> + /* Updates version to the next odd number, indicating
>>> we're writing */
>>> + vcpu->hv_clock.version++;
>>> + kvm_write_guest(vcpu->kvm, vcpu->clock_gpa,
>>> &vcpu->hv_clock, PAGE_SIZE);
>>> +
>>> + kvm_get_msr(vcpu, MSR_IA32_TIME_STAMP_COUNTER,
>>> + &vcpu->hv_clock.last_tsc);
>>> +
>>> + ktime_get_ts(&ts);
>>>
>> Do we need to disable preemption here?
>>
> After thinking for a little while, you are theoretically right.
> In the current state, we could even be preempted between all operations
> ;-) Maybe after avi's suggestion of moving the call to it it will end up
> in a preempt safe region, but anyway, it's safer to add the preempt
> markers here.
> I'll put it in next version, thanks
>
note that you cant call to kvm_write_guest with preemption disabled
(witch you do few lines below)
next prev parent reply other threads:[~2007-11-13 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 22:39 [PATCH 0/3] Kvm clocksource, new spin Glauber de Oliveira Costa
2007-11-08 22:39 ` [PATCH 1/3] include files for kvmclock Glauber de Oliveira Costa
2007-11-08 22:39 ` [PATCH 2/3] kvmclock - the host part Glauber de Oliveira Costa
2007-11-08 22:39 ` [PATCH 3/3] kvmclock implementation, the guest part Glauber de Oliveira Costa
2007-11-11 10:17 ` [PATCH 2/3] kvmclock - the host part Avi Kivity
2007-11-13 11:28 ` Glauber de Oliveira Costa
2007-11-13 14:44 ` Avi Kivity
2007-11-13 5:00 ` [kvm-devel] " Dong, Eddie
2007-11-13 11:54 ` Glauber de Oliveira Costa
2007-11-13 12:08 ` Izik Eidus [this message]
2007-11-13 14:47 ` Avi Kivity
2007-11-13 15:23 ` Dong, Eddie
2007-11-13 16:12 ` Avi Kivity
2007-11-14 0:41 ` Dong, Eddie
2007-11-09 8:37 ` [PATCH 1/3] include files for kvmclock Gerd Hoffmann
2007-11-11 9:15 ` Avi Kivity
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=473993B3.4060508@qumranet.com \
--to=izike@qumranet.com \
--cc=avi@qumranet.com \
--cc=eddie.dong@intel.com \
--cc=gcosta@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=jeremy@goop.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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