similar to: [PATCH] limit ACPIID to APICID reset to AMD machines

Oh, thanks, Niraj. I overlooked this initially, because this code is not implemented in waldi 3.1-2 kernel, but only in 3.3-1. I''ll check it out tonight, as booting a new kernel per remote is a bit too dangerous. This would be exactly what I need. BR, Carsten. Von: Niraj Tolia Gesendet: Mit, 7.1.2009 22:53 An: Carsten Schiers Cc: jbeulich ; mark.langsdorf ; xen-devel Betreff:

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

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

[moderator note: I'm forwarding a stripped down version of the original mail which was rejected in the moderator queue. I stripped the 3.3 megabyte .tar.bz2 of the log file attachment, which is inappropriate for a technical list. Either trim the log to the relevant portion, or host the log externally and have your list email merely give a URL of the externally-hosted file] >

Modify the cpufreq ondemand governor so that it can get idle and total nsecs from the Xen hypervisor.  Xen uses nsecs to measure idle time, while Linux uses ticks. Other than accounting for that difference, use the same algorithm to calculate idle time as Linux does. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> diff -r 26962454b508 drivers/cpufreq/cpufreq_ondemand.c ---

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1321356497 0 # Node ID 3cfb8f2c4ce898414279d7162206be812584bd5b # Parent 955a6c07dc5e9c55316d1678b2b7cc4313f4fd57 xen: avoid crash enabling turbo mode On a system which has not had P-state information pushed down into the hypervisor running "xenpm enable-turbo-mode" will reliably crash the host. (XEN) PM

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

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

With the third generation Opteron parts, AMD switched to an architecturally defined interface for PowerNow! that uses different MSRs than previous versions. This patch brings the PowerNow! driver up to match the mainline Linux driver and provide support for all AMD parts that use or will use the architectural pstate interface. It also removes a WARN_ON statement in kernel/cpu.c that highlights a

On Thu, 30 Sep 2010 14:02:34 +0800, gang.wei@intel.com wrote: > I am the original developer of HPET broadcast code. > > First of all, to disable HPET broadcast, no additional patch is required. > Please simply add option "cpuidle=off" or "max_cstate=1" at xen cmdline in > /boot/grub/grub.conf. > > Second, I noticed that the issue just occur on

Dear libvirt experts, I can not instantiate even a simple machine when using the 'vbox' hypervisor: s14% virt-install --connect=vbox:///session --virt-type vbox --name vtest --memory 500 ERROR cannot obtain CPU freq: No such file or directory s14% virsh -c vbox:///session błąd: cannot obtain CPU freq: No such file or directory (1) How to fix this error? The VirtualBox driver seems

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 +++

At what point is safe to call read_pci_config() in dom0 on x86_64? I''m trying to enable AGP as IOMMU support, and iommu_hole_init() is crashing on the read_pci_config() calls. -Mark Langsdorf AMD, Inc. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

cc1: warnings being treated as errors mpparse.c: In function ''efi_check_config'': mpparse.c:669: error: format ''%08llx'' expects type ''long long unsigned int'', but argument 2 has type ''long unsigned int'' In xen/include/xen/efi.h: 23616: unsigned long mps; /* MPS table */ In xen/arch/x86/mpparse.c (line 669):

it seems getting lost, and thus resend. Thanks, Kevin -----Original Message----- From: Tian, Kevin Sent: 2008年7月24日 8:39 To: ''Jan Beulich'' Cc: Liu, Jinsong; Keir Fraser; xen-devel@lists.xensource.com; mark.langsdorf@amd.com Subject: RE: [Xen-devel] cpufreq info propagation >From: Jan Beulich >Sent: 2008年7月23日 18:13 >> >>startup info is viable. But how

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 list, I have a problem with my new xen server wich can''t reach to start my linux hardware virtual machines which works on my old server without modifications. Here is my situation : On all xen servers (3), I use xen 3.2 for a Dom0 compiled with the linux kernel caming from http://xenbits.xensource.com/linux-2.6.18-xen.hg My 2 old xen servers are : Dual core Intel(R) Pentium(R) D

Hi there, I'm running an ibm xseries 345/dual Xeon 2.66GHz, 2.6.18-53.1.14.el5xen #1 SMP, and cat /proc/cpuinfo shows me only one processor. Apparently something strange happening with ACPI. What am I doing wrong? Thank you! (sorry for the cross post, didn't realize there was a virt list first time around!) Selected bits from dmesg: ------------------------- Using ACPI (MADT) for SMP

Hi there, I'm running an ibm xseries 345/dual Xeon 2.66GHz, 2.6.18-53.1.14.el5xen #1 SMP, and cat /proc/cpuinfo shows me only one processor. Apparently something strange happening with ACPI. What am I doing wrong? Thank you! Selected bits from dmesg: ------------------------- Using ACPI (MADT) for SMP configuration information SMP alternatives: switching to UP code ACPI: Core revision

What if you boot with other kernel? If you have the same result maybe BIOS update is required for your server?! >---------------------------------------------------------------------- > >Message: 1 >Date: Sat, 17 May 2008 14:51:45 -0700 >From: gen2 <gen2 at planetofidiots.com> >Subject: [CentOS-virt] xen kernel showing only one processor on SMP > machine