similar to: RE: Instability with Xen, interrupt routing frozen, HPET broadcast

This follows Linux commit 39fe05e58c5e448601ce46e6b03900d5bf31c4b0, noticing that all this setup is pointless when ARAT support is there, and knowing that on SLED11''s native kernel it has actually caused S3 resume issues. A question would be whether HPET legacy interrupts should be forced off in this case (rather than leaving whatever came from firmware). Signed-off-by: Jan Beulich

The value of ACPI PM-Timer may be broken on save unless the timer mode is delay_for_missed_ticks. With other timer modes, vcpu->arch.hvm_vcpu.guest_time is always zero and the adjustment from its value is wrong. This patch fixes the saved value of ACPI PM-Timer: - don''t adjust the PM-Timer if vcpu->arch.hvm_vcpu.guest_time is zero. - consolidate calculations of PM-Timer to one

On my test machine, in set_time_scale(), the following code: ts->mul_frac = div_frac(MILLISECS(1000), tps32); crashes with a division by zero error if tps32 == 1000000000d. Unfortunately, tps32 is often that value. Does anyone know why this happens? I''ve resolved it temporarily by checking for tps32 == 1000000000 and changing the value slightly (101000010d works fine on my test

Hi all I?ve got a few Intel Z87 chipset machines with Adaptec 5405 raid cards (latest firmware), they work fine on 3.18 but during Dom0 boot using kernel 4.9.13 it hangs at ?Using clocksource tsc? and the aacraid driver keeps trying to reset Has anyone seen anything like this? I?ve tried specifying clocksource=xen in grub instead of the default of tsc, and that has the same issue. HPET is

Modify the cpufreq ondemand governor so that it can get idle and total ticks from the Xen hypervisor. Linux and Xen have different ideas of what an idle tick is, so the Xen values for both have to be returned in the same platform hypercall. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> diff -r b4278beaf354 xen/arch/x86/platform_hypercall.c --- a/xen/arch/x86/platform_hypercall.c

On Sun, Apr 2, 2017 at 9:22 PM, Sarah Newman <srn at prgmr.com> wrote: > On 04/02/2017 02:49 AM, Chris Elliott wrote: >> Hi all >> >> I?ve got a few Intel Z87 chipset machines with Adaptec 5405 raid cards (latest firmware), they work fine on 3.18 but during Dom0 boot using kernel >> 4.9.13 it hangs at ?Using clocksource tsc? and the aacraid driver keeps trying to

On 03/12/2015 13:33, Jonathan Billings wrote: > On Thu, Dec 03, 2015 at 09:29:21AM +0000, Duncan Brown wrote: >> Hi All >> >> After upgrading to 7.2, I'm getting an immediate kernel panic on boot >> >> Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine >> >> How can I go about diagnosing the problem here? > It'd probably

Hi Ian/Stefano: I changed over to the PV clock for hybrid liked we talked at the hackathon. I still have the hang in update_wall_time() after dom0 switches to xen as clocksource. The source of hang seems to be in xen stime_local_stamp in cpu_time that suddenly jumps to a large 64bit value. I''ve been chasing to figure where that happens, and why for the hybrid and not PV. It appears the

These are the diffs against the pristine versions of arch/x86_64/kernel/[aperture.c,pci-gart.c] to better show the changes necessary to adapt those files to Xen. They were included with the patch and should not be applied again. -Mark Langsdorf AMD, Inc. --- pristine-linux-2.6.12/arch/x86_64/kernel/aperture.c 2005-06-17 12:48:29.000000000 -0700 +++

On 03/12/2015 13:54, Jonathan Billings wrote: > On Thu, Dec 03, 2015 at 01:44:47PM +0000, Duncan Brown wrote: >> The last message before it is "switching to clocksource hpet" >> >> Then the panic scrolls by >> >> I've no idea if that counts as later or not > It's unlikely to be a panic related to your hardware clock (HPET = > High Precision

Hello gurus, I have two physical xen hosts and when I migrate a domU from one host to another, I get many of this error from domU kernel: clocksource/0: Time went backwards: delta=-3536123661 shadow=686019823475 offset=281887188 Sometimes domU time stalls and network stops working, but other times it gets working again. The two hosts are using different platform timer source:

I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now" can be

I've been thinking a bit more about how useful an absolute timeout is for a oneshot timer in a virtual environment. In principle, absolute times are generally preferable. A relative timeout means "timeout in X ns from now", but the meaning of "now" is ambiguous, particularly if the vcpu can be preempted at any time, which means the determination of "now" can be

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

In order to support the eventual MFC of a limited and experimental acpi(4) driver from -CURRENT, I have merged a few changes from -CURRENT to -STABLE including: - Power management interface (subr_power.c) - pmtimer(4) driver. Unlike -CURRENT this driver does not require 'device pmtimer' in the kernel config so that existing kernel configs do not have to be changed. - Updated

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1254298855 0 # Node ID 5215da46d60f95d57244e709cb3b189caffec50c # Parent 6472342c8ab0789b844714bcf557e9e5eeacca42 Disable HPET broadcast mode on kexec. Without this the new kernel cannot receive timer interrupts from the legacy sources. Hangs are observed in the second kernel''s "check_timer()"

... by the call to hpet_disable() added in the immediately preceding patch. In order to retain the behavior intended by c/s 23776:0ddb4481f883, implement one of the alternative options pointed out there: remove CPUs from the online map in __stop_this_cpu() (and hence doing so in stop_this_cpu() is no longer needed). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/crash.c

Modify the cpufreq ondemand governor so that it can get idle and total ticks from the Xen hypervisor. Linux and Xen have different ideas of what an idle tick is, so the Xen values for both have to be returned in the same platform hypercall. Otherwise, use basically the same scheme as native Linux. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> iff -r 9bf1ddd0f6bf

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".