similar to: [kvm-devel] [PATCH 0/2][KVM] guest time accounting

The aim of these four patches is to introduce Virtual Machine time accounting. _Ingo_, as these patches modify files of the scheduler, could you have a look to them, please ? [PATCH 1/4] as recent CPUs introduce a third running state, after "user" and "system", we need a new field, "guest", in cpustat to store the time used by the CPU to run virtual CPU. Modify

The aim of these four patches is to introduce Virtual Machine time accounting. _Ingo_, as these patches modify files of the scheduler, could you have a look to them, please ? [PATCH 1/4] as recent CPUs introduce a third running state, after "user" and "system", we need a new field, "guest", in cpustat to store the time used by the CPU to run virtual CPU. Modify

[PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest i= f we are running a VCPU. We add this cputime to cpustat->user instead of cpustat->system because this part of KVM code is in fact user code although= it is executed in the kernel. We duplicate VCPU time between guest and user to allow an unmodified "top(1)" to display correct value. A modified

[PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest i= f we are running a VCPU. We add this cputime to cpustat->user instead of cpustat->system because this part of KVM code is in fact user code although= it is executed in the kernel. We duplicate VCPU time between guest and user to allow an unmodified "top(1)" to display correct value. A modified

[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task= ) and "cgtime" (guest time of the task children) fields for the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis= play these new fields. Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net --------------

[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task= ) and "cgtime" (guest time of the task children) fields for the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis= play these new fields. Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net --------------

http://libvirt.org/html/libvirt-libvirt.html#virDomainInfo http://libvirt.org/html/libvirt-libvirt.html#virVcpuInfo Both virDomainInfo and virVcpuInfo have a nanosecond cpuTime field. How do the two related to one another? With some experiementing, it appears the virDomainInfo::cpuTime is equal to the host CPU time used by the qemu-kvm process for the domain. It also appears that the

In a virtualized environment, virtual machines will time share the system with each other and with other processes running on the host system. Therefore, a VM's virtual CPUs (VCPUs) will be executing on the host's physical CPUs (pcpus) for only some portion of time. The VMI exposes a paravirtual view of time to the guest operating systems so that they may operate more effectively in a

In a virtualized environment, virtual machines will time share the system with each other and with other processes running on the host system. Therefore, a VM's virtual CPUs (VCPUs) will be executing on the host's physical CPUs (pcpus) for only some portion of time. The VMI exposes a paravirtual view of time to the guest operating systems so that they may operate more effectively in a

Hi, I am not sure, but I think this may be a process accounting bug. If interrupts are disabled for a considerable amount of time ( say multiple ticks), the process accounting code will still account a single tick for such cases, on the next interrupt tick. Shouldn't we have some way to fix that case like we do for NO_HZ restart_sched_tick case, where we account for multiple idle ticks.

Hi, I am not sure, but I think this may be a process accounting bug. If interrupts are disabled for a considerable amount of time ( say multiple ticks), the process accounting code will still account a single tick for such cases, on the next interrupt tick. Shouldn't we have some way to fix that case like we do for NO_HZ restart_sched_tick case, where we account for multiple idle ticks.

Hi, It's unfortunate that with recent revisions of R 2.13 (this appeared in revision 54640, March 2), 'R CMD build' now removes empty dirs in the package. People might have good reasons for having empty dirs in their packages. For example, in Bioconductor, we have some tools to automatically generate annotation packages and those tools are implemented in software packages that use

Hi,all I want to get a relatively accurate cpu usage of a domain. I have a few questions about virDomainGetInfo: struct virDomainInfo{ unsigned char state : //the running state, one of virDomainState unsigned long maxMem :// the maximum memory in KBytes allowed unsigned long memory :// the memory in KBytes used by the domain unsigned short nrVirtCpu :// the number of virtual CPUs for the

I have a data-set that is structured as follows: sp wg n v.realtime v.cputime v.tcputime v.idletime v.nswtch 9 0 1 1 28.61300 28.61 28.6039 0.00000e+00 407 1563 0 1 2 15.20270 30.38 28.5981 9.80523e-01 483 3128 0 1 4 12.50930 50.00 28.6053 1.07877e+01 489 4682 0 1 6 12.10260 72.55

Hi all, this patch series introduces stolen ticks accounting for Xen on ARM. Stolen ticks are clocksource ticks that have been "stolen" from the cpu, typically because Linux is running in a virtual machine and the vcpu has been descheduled. To account for these ticks we introduce CONFIG_PARAVIRT and pv_time_ops so that we can make use of:

On Fri, Nov 03, 2017 at 06:48:11AM -0700, Johnny Hughes wrote: > On 11/02/2017 03:38 PM, Fred Smith wrote: > > On Thu, Nov 02, 2017 at 02:09:04PM -0400, m.roth at 5-cent.us wrote: > >> Yves Bellefeuille wrote: > >>> Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > >>> > >>>> Not intending to contradict (if that ends up as pain,

Hi! I'm comparing the cpu usage of a VM from virDomainGetInfo and the usages returned per-vcpu from virDomainGetVcpus and the totals do not match up. I expect that the cpu usages reported per-vcpu, when summed, should equal the total cpu usage of the domain, but there is quite a large gap between them. Is there something I'm missing? See this example code using the python

Using an rsync (V2.5.6, Tru64 Unix 5.1A) command of the form: rsync -avz --delete /some/dir remhost:/some/other/dir where /some/dir has about 460,000 files in it, I get: building file list ... done ERROR: out of memory in make_file rsync error: error allocating core memory buffers (code 22) at /usr/common/src/rsync-2.5.6/util.c(115) rsync: connection unexpectedly closed (8 bytes read so far)

Last week we installed Samba 3.0.20b on one of our servers, worked fine and does it's job well. But today the load was rising due two smbd processes taking up all cputime. While looking for hints on what was going on the logfiles show two types of errors (I don't know at this time if it has anything to do with the load spike): lib/util_sock.c:write_data(554) write_data: write failure in

Someone recently suggested building a system for automatically testing student's R programs. They would upload them to our Virtual Learning Environment, which would then run the code on some inputs and see if it got the right output. If it does, the student scores points for that course. My first thought was "you want to run unchecked, student-submitted code on a server that has access