search for: cur_timer

Does this look okay? : Time: 1:15.50 of 4:13.73, Bitrate: 133.3 How about? : <snip from=ogg123.c> info.u_time = ov_time_total (&vf, -1); /* Seconds with double precision */ gettimeofday (&start_time, NULL); t_min = (long) info.u_time / (long) 60; t_sec = info.u_time - 60 * t_min; while (! eos) { gettimeofday (&cur_time, NULL); c_min = (long)

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

...14 15:05:28 2007 -0400 @@ -60,6 +60,16 @@ struct cpu_time { static DEFINE_PER_CPU(struct cpu_time, cpu_time); +struct plt_timer_ops { + char* name; + int (*init)(void); + u64 (*read_count)(void); + void (*suspend)(void); + void (*resume)(void); +}; + +struct plt_timer_ops *cur_timer; + /* * Protected by platform_timer_lock, which must be acquired with interrupts * disabled because pit_overflow() is called from PIT ch0 interrupt context. @@ -68,7 +78,6 @@ static u64 platform_timer_stamp; static u64 platform_timer_stamp; static struct time_scale platform_timer_scale; sta...

There are several bugs at error path of create_snapshot() when the transaction commitment failed. - access the freed transaction handler. At the end of the transaction commitment, the transaction handler was freed, so we should not access it after the transaction commitment. - we were not aware of the error which happened during the snapshot creation if we submitted a async transaction

...;Using HPET for base-timer\n"); } @@ -479,11 +484,6 @@ void __init time_init(void) return; } #endif - xtime.tv_sec = get_cmos_time(); - xtime.tv_nsec = (INITIAL_JIFFIES % HZ) * (NSEC_PER_SEC / HZ); - set_normalized_timespec(&wall_to_monotonic, - -xtime.tv_sec, -xtime.tv_nsec); - cur_timer = select_timer(); printk(KERN_INFO "Using %s for high-res timesource\n",cur_timer->name); Index: linux-2.6.16-rc6/arch/i386/kernel/timers/common.c =================================================================== --- linux-2.6.16-rc6.orig/arch/i386/kernel/timers/common.c 2006-01-...

...;Using HPET for base-timer\n"); } @@ -479,11 +484,6 @@ void __init time_init(void) return; } #endif - xtime.tv_sec = get_cmos_time(); - xtime.tv_nsec = (INITIAL_JIFFIES % HZ) * (NSEC_PER_SEC / HZ); - set_normalized_timespec(&wall_to_monotonic, - -xtime.tv_sec, -xtime.tv_nsec); - cur_timer = select_timer(); printk(KERN_INFO "Using %s for high-res timesource\n",cur_timer->name); Index: linux-2.6.16-rc6/arch/i386/kernel/timers/common.c =================================================================== --- linux-2.6.16-rc6.orig/arch/i386/kernel/timers/common.c 2006-01-...

Clean up btrfs_lookup_dentry() to never return NULL, but PTR_ERR(-ENOENT) instead. This keeps the return value convention consistent. Callers who use btrfs_lookup_dentry() require a trivial update. create_snapshot() in particular looks like it can also lose a BUG_ON(!inode) which is not really needed - there seems less harm in returning ENOENT to userspace at that point in the stack than there

From: Anand <anand.jain@oracle.com> This patch adds creation-time to the snapshot list display, which would help user to better manage the snapshots when number of snapshots grow substantially. This patch is developed and on top of the send/receive btrfs and btrfs-progs repo at git://github.com/ablock84/linux-btrfs.git (send-v2) git://github.com/ablock84/btrfs-progs.git (send-v2)

...========================================================= --- linux-2.6.16-rc6.orig/include/asm-i386/timer.h 2006-03-12 19:57:42.000000000 -0800 +++ linux-2.6.16-rc6/include/asm-i386/timer.h 2006-03-12 19:57:48.000000000 -0800 @@ -48,6 +48,8 @@ extern int pit_latch_buggy; extern struct timer_opts *cur_timer; extern int timer_ack; +extern int use_sched_clock_cycles; + /* list of externed timers */ extern struct timer_opts timer_none; extern struct timer_opts timer_pit; @@ -70,9 +72,18 @@ extern unsigned long calibrate_tsc_hpet( extern struct init_timer_opts timer_pmtmr_init; #endif +#ifdef CO...

...========================================================= --- linux-2.6.16-rc6.orig/include/asm-i386/timer.h 2006-03-12 19:57:42.000000000 -0800 +++ linux-2.6.16-rc6/include/asm-i386/timer.h 2006-03-12 19:57:48.000000000 -0800 @@ -48,6 +48,8 @@ extern int pit_latch_buggy; extern struct timer_opts *cur_timer; extern int timer_ack; +extern int use_sched_clock_cycles; + /* list of externed timers */ extern struct timer_opts timer_none; extern struct timer_opts timer_pit; @@ -70,9 +72,18 @@ extern unsigned long calibrate_tsc_hpet( extern struct init_timer_opts timer_pmtmr_init; #endif +#ifdef CO...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths