linux-kernel - Re: [PATCH] x86/kvm: Show guest system/user cputime in cpustat

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:	Thu, 11 Mar 2010 09:36:01 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Sheng Yang <sheng@...ux.intel.com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH] x86/kvm: Show guest system/user cputime in cpustat

On 03/11/2010 09:20 AM, Sheng Yang wrote:
> Currently we can only get the cpu_stat of whole guest as one. This patch
> enhanced cpu_stat with more detail, has guest_system and guest_user cpu time
> statistics with a little overhead.
>
> Signed-off-by: Sheng Yang<sheng@...ux.intel.com>
> ---
>
> This draft patch based on KVM upstream to show the idea. I would split it into
> more kernel friendly version later.
>
> The overhead is, the cost of get_cpl() after each exit from guest.
>    

This can be very expensive in the nested virtualization case, so I 
wouldn't like this to be in normal paths.  I think detailed profiling 
like that can be left to 'perf kvm', which only has overhead if enabled 
at runtime.

For example you can put the code to note the cpl in a tracepoint which 
is enabled dynamically.

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