search for: cpu_process

...do? And by the way: I found no code that TSC will get adjusted, so I think it will get worse over the time... Thanks, Carsten. messages.0:Jan 9 12:25:15 data kernel: Timer ISR/1: Time went backwards: delta=-12018171 delta_cpu=115981829 shadow=75780489375160 off=410607630 processed=75780912000000 cpu_processed=75780784000000 messages.0:Jan 9 12:25:16 data kernel: Timer ISR/1: Time went backwards: delta=-16026092 delta_cpu=75973908 shadow=75780489375160 off=806599392 processed=75781312000000 cpu_processed=75781220000000 messages.0:Jan 9 12:25:17 data kernel: Timer ISR/0: Time went backwards: delta=-74...

After installing a Phenom II X4 processor (replacing a single core Semperon) I am getting these messages on the console and in dmesg: Warning Timer ISR/2: Time went backwards: delta=-250135996 delta_cpu=13864004 shadow=1355887856733 off=870052783 processed=1357008044419 cpu_processed=1356744044419 0: 1357004044419 1: 1356696044419 2: 1356744044419 3: 1356696044419 printk: 41 messages suppressed. Warning Timer ISR/1: Time went backwards: delta=-59982686 delta_cpu=4017314 shadow=1360903191494 off=777060324 processed=1361740044419 cpu_processed=1361676044419 0: 136174004441...

...essage, that shadow->system_timestamp+offset is significantly behind the previous value of processed_system_time, and that the previous value was set by the OTHER vcpu. Timer ISR/0: Time went backwards: delta=-44611438 cpu_delta=15388562 shadow=69081255546 off=254172405 processed=69380039389 cpu_processed=69320039389 last_modified=CPU1, prev_st=69291796314, prev_offset=92519230 0: 69320039389 1: 69380000000 Timer ISR/0: Time went backwards: delta=-1374402 cpu_delta=528625598 shadow=69081255546 off=777409441 processed=69860039389 cpu_processed=69330039389 last_modified=CPU1, prev_st=69291796314,...

Enable cpufreq support in Xen for AMD Operton processors by: 1) Allowing the PowerNow! driver in dom0 to write to the PowerNow! MSRs. 2) Adding the cpufreq notifier chain to time-xen.c in dom0. On a frequency change, a platform hypercall is performed to scale the frequency multiplier in the hypervisor. 3) Adding a platform hypercall to the hypervisor the scale the frequency multiplier and reset

Hello ! Does anybody know how to build and use cpufreq support that should be in 3.2 since -unstable time ? Bye -- __________________________________________________ Ralf Schenk fon (02 41) 9 91 21-0 fax (02 41) 9 91 21-59 rs@databay.de Databay AG Hüttenstraße 7 D-52068 Aachen www.databay.de Vorstand: Jens Conze, Ralf Schenk, Aresch Yavari Aufsichtsratvorsitzender: Ansgar Vögeli

...-348.3.1.el5, and after booting into the new kernel, noted large amounts of these messages every second or so in the logs: Mar 30 21:38:35 atlas2 kernel: Warning Timer ISR/0: Time went backwards: delta=-1393683849 delta_cpu=22316151 shadow=225003685197135 off=129240997 processed=225005208029053 cpu_processed=225003792029053 On both the dom0 and the domUs. Some reading indicates that this _was_ a fault fixed in 2009/2010, but it seems to have resurfaced on the latest kernel. For now, we've reverted back to an earlier kernel. Has anybody else seen this recently, or got any insight? Thanks, Da...

Hi all, Using a slow serial console with sync_console on SMP leaves me with an unusable system: it gets into a flood of Timer ISR/0: Time went backwards: delta=-3566279 cpu_delta=16433721 shadow=2019998373 off=420435384 processed=2444000000 cpu_processed=2424000000 0: 2424000000 1: 2444000000 messages which swamps the console and leaves things almost, but not quite, completely hung. It is a simple matter to ratelimit these printks, which completely eliminates the problem for me. Cheers, Stephen ___________________________________________...

...21:27:43 debian37 kernel: xenbr0: port 3(vif6.0) entering forwarding state Aug 18 21:27:44 debian37 kernel: printk: 161 messages suppressed. Aug 18 21:27:44 debian37 kernel: Timer ISR/1: Time went backwards: delta=-36922242 delta_cpu=51077758 shadow=918553 off=3534535644052 processed=3534572000000 cpu_processed=3534484000000 Aug 18 21:27:44 debian37 kernel: 0: 3534572000000 Aug 18 21:27:44 debian37 kernel: 1: 3534484000000 ----------------------------------------------------------------------- This is the output of "/proc/cpuinfo": ----------------------------------------------------------...

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP and SMP guest support (NEW!) * dynamic ticks (NEW!) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes (non-PAE may be broken at the moment) * xen hvc console

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP and SMP guest support (NEW!) * dynamic ticks (NEW!) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes (non-PAE may be broken at the moment) * xen hvc console

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP and SMP guest support (NEW!) * dynamic ticks (NEW!) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes (non-PAE may be broken at the moment) * xen hvc console

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

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual