[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46C7F362.80106@qumranet.com>
Date: Sun, 19 Aug 2007 10:38:10 +0300
From: Avi Kivity <avi@...ranet.com>
To: Laurent Vivier <Laurent.Vivier@...l.net>
CC: Rusty Russell <rusty@...tcorp.com.au>,
kvm-devel <kvm-devel@...ts.sourceforge.net>,
linux-kernel <linux-kernel@...r.kernel.org>,
virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [kvm-devel] [PATCH/RFC 3/4]Introduce "account modifiers" mechanism
Laurent Vivier wrote:
> Avi Kivity wrote:
> [...]
>
>> The normal user/system accounting has the same issue, no? Whereever we
>> happen to land (kernel or user) gets the whole tick.
>>
>> So I think it is okay to have the same limitation for guest time.
>>
>>
>
> So this is how it looks like.
> PATCH 1 and 2 are always a prerequisite.
>
>
> + tmp = cputime_to_cputime64(cputime);
> + if (p->flags & PF_VCPU) {
> + p->utime = cputime_add(p->utime, cputime);
> + p->gtime = cputime_add(p->gtime, cputime);
> +
> + cpustat->guest = cputime64_add(cpustat->guest, tmp);
> + cpustat->user = cputime64_add(cpustat->user, tmp);
> +
> + p->flags &= ~PF_VCPU;
> +
> + return;
> + }
> +
Where did CONFIG_GUEST_ACCOUNTING go?
--
error compiling committee.c: too many arguments to function
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists