search for: softtsc

Various versions of Linux under various circumstances select TSC as the primary clocksource for the kernel. This is especially true for uniprocessor kernels, but also in some cases for multiprocessor kernels. In most cases, this is because a processor bit (tsc_invariant? constant_tsc?) is passed through directly from the hardware via Xen and tested by the hvm guest and the result implies that

Hi, I have done some debugging to find out the root cause of bug 1282, which has the following symptoms with paravirtualized guests: - after a live migrate, the time on the guest can jump - after a live migrate, the guest "forgets" to wake up processes - after a domU save, dom0 reboot and domU restore, the time is correct but processes are not woken up from sys_nanosleep The problem

...') => dump iommu p2m table (XEN) key ''q'' (ascii ''71'') => dump domain (and guest debug) info (XEN) key ''r'' (ascii ''72'') => dump run queues (XEN) key ''s'' (ascii ''73'') => dump softtsc stats (XEN) key ''t'' (ascii ''74'') => display multi-cpu clock info (XEN) key ''u'' (ascii ''75'') => dump numa info (XEN) key ''v'' (ascii ''76'') => dump Intel''s VMCS (XEN) key &...

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have