From: Avi Kivity <avi@qumranet.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: Ingo Molnar <mingo@elte.hu>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [kvm-devel] [PATCH 4/4] Modify KVM to update guest time accounting.
Date: Mon, 20 Aug 2007 17:08:23 +0300 [thread overview]
Message-ID: <46C9A057.6060303@qumranet.com> (raw)
In-Reply-To: <46C99C05.90701@bull.net>
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Laurent Vivier wrote:
>>
>>> [PATCH 4/4] Modify KVM to update guest time accounting.
>>>
>>>
>>>
>>> Index: kvm/drivers/kvm/kvm.h
>>> ===================================================================
>>> --- kvm.orig/drivers/kvm/kvm.h 2007-08-20 13:23:53.000000000 +0200
>>> +++ kvm/drivers/kvm/kvm.h 2007-08-20 13:23:58.000000000 +0200
>>> @@ -589,6 +589,17 @@ void kvm_mmu_unload(struct kvm_vcpu *vcp
>>>
>>> int kvm_hypercall(struct kvm_vcpu *vcpu, struct kvm_run *run);
>>>
>>> +static inline void kvm_guest_enter(void)
>>> +{
>>> +#ifdef CONFIG_GUEST_ACCOUNTING
>>> + current->flags |= PF_VCPU;
>>> +#endif
>>>
>>>
>> Since you select GUEST_ACCOUNTING, the #ifdef is always true?
>>
>
> It is just to avoid error if we compile kvm module outside of the kernel, with
> kernel without support of guest accounting. Can be removed if you want.
>
>
Ah okay. We take care of the external module in
external-module-compat.h (in this case, we can #define PF_VCPU to 0 if
it is undefined).
>>> +}
>>> +
>>> +static inline void kvm_guest_exit(void)
>>> +{
>>>
>>>
>> Missing content?
>>
>
> No, empty function.
>
> It is just to introduce "symmetry" in code, the VCPU code begins with
> "kvm_guest_start()" and ends with "kvm_guest_exit()". And we have no operation
> to do in kvm_guest_exit() (the PF_VCPU is cleared by account_system_time()), so
> "empty function", removed by the optimizer (I hope).
>
But what if account_system_time() is not called (because we exited
before the timer interrupt hit)?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-08-20 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:14 Laurent Vivier
2007-08-20 13:40 ` [kvm-devel] " Avi Kivity
2007-08-20 13:49 ` Laurent Vivier
2007-08-20 14:08 ` Avi Kivity [this message]
2007-08-20 14:22 ` Laurent Vivier
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=46C9A057.6060303@qumranet.com \
--to=avi@qumranet.com \
--cc=Laurent.Vivier@bull.net \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.linux-foundation.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
Powered by JetHome