search for: wallclock

The initial values of the wallclock time in the shared info page are set for PVHVM guests when the hypercall page is initialized, since the hypercall page is not reinitialized on resume, the hypervisor wallclock time is not properly set on resume. Fix it by forcing an update of the wallclock values when the shared info page is mappe...

...g directory `/home/eric/xapian-bindings-1.2.21/perl' make check-am make[2]: Entering directory `/home/eric/xapian-bindings-1.2.21/perl' make check-TESTS make[3]: Entering directory `/home/eric/xapian-bindings-1.2.21/perl' ./t/01use.t .. ok All tests successful. Files=1, Tests=3, 0 wallclock secs ( 0.12 usr 0.02 sys + 0.23 cusr 0.02 csys = 0.39 CPU) Result: PASS PASS: t/01use.t ./t/02pod.t .. skipped: set TEST_POD to enable this test Files=1, Tests=0, 0 wallclock secs ( 0.12 usr 0.01 sys + 0.21 cusr 0.01 csys = 0.35 CPU) Result: NOTESTS PASS: t/02pod.t ./t/03podcoverage.t .. s...

Hi All, I have just started looking at the code for Xen so please bear with me. A domU Linux kernel running with independent_wallclock=1 seems to sync its time with dom0 after every "xm unpause" (obviously preceded by an "xm pause"). I don''t see where the xtime variable is being updated after an "xm unpause", i.e., domain_unpause_by_systemcontroller(). Right after the unpause, it seems t...

Call update_domain_wallclock_time on hvm_latch_shinfo_size even if the bitness of the guest has already been set, this fixes the problem with the wallclock not being set for PVHVM guests on resume from migration. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Keir Fra...

The paravirtualized guests are offered wallclock time referenced to UTC only, while fully virtualized guests are given the option via the config file (localtime parameter) of starting with UTC time or local time. What would it take to optionally provide localtime to the paravirtualized guests as well? For a guest that launches assuming localtime...

From: David Vrabel <david.vrabel@citrix.com> The high resolution timer code gets notified of step changes to the system time with clock_was_set() or clock_was_set_delayed() calls. If other parts of the kernel require similar notification there is no clear place to hook into. Add a clock_was_set atomic notifier chain (clock_was_set_notifier_list) and call this in place of clock_was_set().

...DEBUG_PAGE_TYPE #ifdef CONFIG_X86_PAE @@ -714,7 +705,6 @@ do { \ vmi_ops.cache = (void *)rel->eip; \ } \ } while (0) - /* * Activate the VMI interface and switch into paravirtualized mode @@ -894,8 +884,8 @@ static inline int __init activate_vmi(vo paravirt_ops.get_wallclock = vmi_get_wallclock; paravirt_ops.set_wallclock = vmi_set_wallclock; #ifdef CONFIG_X86_LOCAL_APIC - paravirt_ops.setup_boot_clock = vmi_timer_setup_boot_alarm; - paravirt_ops.setup_secondary_clock = vmi_timer_setup_secondary_alarm; + paravirt_ops.setup_boot_clock = vmi_time_bsp_init; + par...

...DEBUG_PAGE_TYPE #ifdef CONFIG_X86_PAE @@ -714,7 +705,6 @@ do { \ vmi_ops.cache = (void *)rel->eip; \ } \ } while (0) - /* * Activate the VMI interface and switch into paravirtualized mode @@ -894,8 +884,8 @@ static inline int __init activate_vmi(vo paravirt_ops.get_wallclock = vmi_get_wallclock; paravirt_ops.set_wallclock = vmi_set_wallclock; #ifdef CONFIG_X86_LOCAL_APIC - paravirt_ops.setup_boot_clock = vmi_timer_setup_boot_alarm; - paravirt_ops.setup_secondary_clock = vmi_timer_setup_secondary_alarm; + paravirt_ops.setup_boot_clock = vmi_time_bsp_init; + par...

Hi, having running centOS-4.4 on a really fast machine (16 GB memory, 8 Opteron CPU's, SATA drives). Then making an update by using the Centos-5 CD's. The start was fast, but during update, the installer spents a very, very long wallclock time during selinx updating: for about 1/2 hour the updater runs in a restorecon/find sequence. And at the end, before the MBR is written, it spents again a long time in "install". Can somebody explain this? Regards -- Joachim Backes <joachim.backes at rhrk.uni-kl.de> Universit...

...The disk drives are 500 GB SATA-Drives. Wondering about times for dd command performance and rm command performance in an empty machine (the filesystem has been made with "mkfs.ext3 /dev/sd...", nothing more) 1. Making a new 3 GB (1024 x 3megabytes blocks) file with dd needs 10.18 sec wallclock time: taskset 1 time dd if=/dev/zero bs=3M count=1024 of=~backes/xxxxx 1024+0 records in 1024+0 records out 0.00user 10.02system 0:10.18elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+187minor)pagefaults 0swaps 2. Repeating the same for 3 times: taskset 1 time dd if=/...

--- common/include/test-tvdiff.c | 75 +++++++++++++++++++++++++++++------- common/include/tvdiff.h | 13 ++++++- 2 files changed, 74 insertions(+), 14 deletions(-) diff --git a/common/include/test-tvdiff.c b/common/include/test-tvdiff.c index 9cbcfc0..abefb2e 100644 --- a/common/include/test-tvdiff.c +++ b/common/include/test-tvdiff.c @@ -36,7 +36,6 @@ #include <stdlib.h> #include

...PU is in the 'ready' state, and does not progress otherwise. Available time is defined per VCPU to progress at the rate of real time when the VCPU is in the 'running' and 'halted' states, and does not progress when the VCPU is in the 'ready' state. Additionally, the wallclock time is provided by the VMI. See the VMI specification for more details. This patch provides a Linux time source, the VMI Time device, that is programmed against the cycle counters and alarms provided by the VMI. It is used as the time source when the kernel detects the presence of a hypervisor....

...PU is in the 'ready' state, and does not progress otherwise. Available time is defined per VCPU to progress at the rate of real time when the VCPU is in the 'running' and 'halted' states, and does not progress when the VCPU is in the 'ready' state. Additionally, the wallclock time is provided by the VMI. See the VMI specification for more details. This patch provides a Linux time source, the VMI Time device, that is programmed against the cycle counters and alarms provided by the VMI. It is used as the time source when the kernel detects the presence of a hypervisor....

Hi, Is anyone aware of existing discussion on embedding the actual wall time (as in RFC-822 date-time) into Ogg streams of continuous or semi-continuous recordings? And any methods of addressing Ogg streams by the wall time in lieu of a standard timecode? Ideally, users would be able to take note of the wall time during an event of interest, then retrieve the segment by that same wall time

More goo from hrtimers integration. We do compile and run properly with NO_HZ enabled. There was a period when we didn't because of a missing export, but that was since fixed. And with the clocksource code now firmly in place, we can get rid of code that fixes up the wallclock, since this is done in the common infrastructure. This actually fixes a timer bug as well, that was caused by do_settimeofday no longer being callable with interrupts disabled due to the use of on_each_cpu(). Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 5d41588419ab arch/i386/Kco...

Does anybody know if it's possible to have R send an email or execute an additional line of code in case an error is generated from a running script? I am running R on a cluster and would like to have it kill the job if R generates an error, but as it is, the job just keeps running until the wallclock is done. Thanks. -- View this message in context: http://www.nabble.com/email-notification-after-error-tp24963220p24963220.html Sent from the R help mailing list archive at Nabble.com.

During norml operation this morning we're seeing a significantly increased load on the IMAP server (factor 5, from 5 to 25). Does dovecot need to rebuild index files or perform other IO intensive operations after the upgrade? We're using Maildir Our monitoring shows increased "system" time. We're runnign fewer processes, the IO rate ist identical to yesterday, memory usage

More goo from hrtimers integration. We do compile and run properly with NO_HZ enabled. There was a period when we didn't because of a missing export, but that was since fixed. And with the clocksource code now firmly in place, we can get rid of code that fixes up the wallclock, since this is done in the common infrastructure. This actually fixes a timer bug as well, that was caused by do_settimeofday no longer being callable with interrupts disabled due to the use of on_each_cpu(). Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 5d41588419ab arch/i386/Kco...

Either wallclock time, uptime or time since client connection can be reflected back to the client in a big endian binary structure. $ nbdkit reflection time --run 'nbdsh --connect $uri -c "sys.stdout.buffer.write(h.pread(12,0))" | hexdump -C' 00000000 00 00 00 00 5d 8f 24 c7 00 04 24 01...

Either wallclock time, uptime or time since client connection can be served back to the client in a big endian binary structure. $ nbdkit info time --run 'nbdsh --connect $uri -c "sys.stdout.buffer.write(h.pread(12,0))" | hexdump -C' 00000000 00 00 00 00 5d 8f 24 c7 00 04 24 01...