[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] clocksource - XenServer 7 - AKA xen 4.6.1
Hello, I was looking at my xen server clock source and I see: xl dmesg | grep -i timer (XEN) [ 3.306920] Platform timer is 14.318MHz HPET I have a E5420 and I have ran into clocksource issues with proxmox/kvm so I was wondering about some things while reading this documentation: https://wiki.xen.org/wiki/Xen_power_management#System_time.2FTSC_skew Quote: "If TSC frequency is invariant across freq/voltage scaling (true for all Intel processors supporting VTx) and all processors within the box share one crystal, please give boot option 'consistent_tscs'." Is that really true? There is no shutdown/slowdown/suspend of the tsc clock with VT processors? The only reason I ask is because of the proxmox (kvm) issue I was having and I think I had to disable speed step on the system to fix at the time. It was an i5 proc w/ VT-x...no VT-d though. I actually get more and more confused the more I read about CPU timers. I have a CPU intensive domU python application that seems to need a more high precision timer then it has right now. It reads the current time, does something, and the reads again and if both reads are the same (which I think they are) it crashes. I always thought that tsc was more precise but (as I said i was getting confused) I just read something that says that HPET was more precise. It could be that I do not need precision but instead the speed so it increments. But I cannot understand how a clock on a CPU (that does not follow the speed step stuff or power save stuff) cannot be accurate. Reading this: http://stackoverflow.com/questions/13950264/does-using-tsc-as-clock-source-improve-timer-and-scheduling-granularity Quote: "remember that Time stamp counter is incremented at every CPU clock cycle." CPU clock cycle > HPET It does go on to talk about the tsc issues that have to do with idle states, scaling, and power but none of this applies to me right? (right?) Any suggestions on what I should do here or which is better? Why is xen 4.6.1 choosing HPET as default? Also even if I switch over to tsc or constant_tsc is the xen clocksource in the domU able to handle the higher clock rate of a tsc based timer? Last question I have: It looks like I have to select my clocksource in xen with clocksource=hpet/acpi/pit That is from https://wiki.xen.orghpet=disable/wiki/Xen_power_management#Xen_hypervisor_clocksource_option but it does not mention tsc there. It also does not mention a way to figure out what clocksource methods that the hardware supports. Is there a way to figure out what the hardware supports without running a live cd or something? _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx https://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |