search for: frequencey

Displaying 4 results from an estimated 4 matches for "frequencey".

Did you mean: frequence
2011 Jul 01
1
NUT PSU/IPMI driver using FreeIPMI (was: [Freeipmi-devel] in need of guidance...)
...rrent: 0 Amps FRU Power Supply Inrush Interval: 0 ms FRU Power Supply Low End Input Voltage 1: 90000 mV FRU Power Supply High End Input Voltage 1: 264000 mV FRU Power Supply Low End Input Voltage 2: 0 mV FRU Power Supply High End Input Voltage 2: 0 mV FRU Power Supply Low End Acceptable Frequencey: 47 Hz FRU Power Supply High End Acceptable Frequencey: 63 Hz FRU Power Supply A/C Dropout Tolerance: 0 ms FRU Power Supply Predictive Fail Support: No FRU Power Supply Power Factor Correction Supported: No FRU Power Supply AutoSwitch Supprt: Yes FRU Power Supply Hot Swap Support: Yes...
2017 Feb 08
0
[PATCH 2/2] locking/mutex, rwsem: Reduce vcpu_is_preempted() calling frequency
...lock(); while (__mutex_owner(lock) == owner) { @@ -436,9 +437,11 @@ bool mutex_spin_on_owner(struct mutex *lock, struct task_struct *owner, /* * Use vcpu_is_preempted to detect lock holder preemption issue. + * As vcpu_is_preempted is more costly to use, it is called at + * a reduced frequencey (once every 256 iterations). */ if (!owner->on_cpu || need_resched() || - vcpu_is_preempted(task_cpu(owner))) { + (!(++loop & 0xff) && vcpu_is_preempted(task_cpu(owner)))) { ret = false; break; } diff --git a/kernel/locking/rwsem-xadd.c b/kernel/locking/rwsem...
2017 Feb 08
4
[PATCH 1/2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
It was found when running fio sequential write test with a XFS ramdisk on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 71.27% 0.28% fio [k] down_write 70.99% 0.01% fio [k] call_rwsem_down_write_failed 69.43% 1.18% fio [k] rwsem_down_write_failed 65.51% 54.57% fio [k] osq_lock 9.72% 7.99% fio [k] __raw_callee_save___kvm_vcpu_is_preempted 4.16%
2017 Feb 08
4
[PATCH 1/2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
It was found when running fio sequential write test with a XFS ramdisk on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 71.27% 0.28% fio [k] down_write 70.99% 0.01% fio [k] call_rwsem_down_write_failed 69.43% 1.18% fio [k] rwsem_down_write_failed 65.51% 54.57% fio [k] osq_lock 9.72% 7.99% fio [k] __raw_callee_save___kvm_vcpu_is_preempted 4.16%