lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 4 Aug 2009 20:12:20 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Laurent Vivier <Laurent.Vivier@...l.net>,
	Ingo Molnar <mingo@...e.hu>,
	kvm-devel <kvm-devel@...ts.sourceforge.net>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [PATCH 0/4] Virtual Machine Time Accounting

On Tue, 04 Aug 2009 19:33:14 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> On Tue, 2009-08-04 at 19:29 +0200, Martin Schwidefsky wrote:
> 
> > > So its going to split user time into user and guest. Does that really
> > > make sense? For the host kernel it really is just another user process,
> > > no?
> > 
> > The code (at least in parts) is already upstream. Look at the
> > account_guest_time function:
> > 
> > static void account_guest_time(struct task_struct *p, cputime_t cputime,
> >                                cputime_t cputime_scaled)
> > {
> >         cputime64_t tmp;
> >         struct cpu_usage_stat *cpustat = &kstat_this_cpu.cpustat;
> > 
> >         tmp = cputime_to_cputime64(cputime);
> > 
> >         /* Add guest time to process. */
> >         p->utime = cputime_add(p->utime, cputime);
> >         p->utimescaled = cputime_add(p->utimescaled, cputime_scaled);
> >         account_group_user_time(p, cputime);
> >         p->gtime = cputime_add(p->gtime, cputime);
> > 
> >         /* Add guest time to cpustat. */
> >         cpustat->user = cputime64_add(cpustat->user, tmp);
> >         cpustat->guest = cputime64_add(cpustat->guest, tmp);
> > }
> > 
> > The cpu time for a guest is added to p->utime AND p->gtime. That is
> > done not to break existing tools that know nothing about guest time.
> > A guest time aware tool can subtract the p->gtime from p->utime to
> > get the time spent by the process outside of the guest context.
> 
> But why? How a vcpu anything other than yet another userspace process?

Because you have two different contexts where you spent time, the
"normal" process context and the "guest" process context. To know how
much of your cpu time is spent on virtualization overhead is an
interesting number.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ