similar to: How to use Px/Cx for power saving?

Hi, This patch is enabling write access during rom_scan. Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Best Regards, Akio Takebe _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I got the following compilation error. This patch fix the error, I think it is needed for xen-testing tree. /root/unstable/linux-2.6.18-xen.hg/scripts/mod/sumversion.c: In function ''get_src_version'': /root/unstable/linux-2.6.18-xen.hg/scripts/mod/sumversion.c:384: error: ''PATH_MAX'' undeclared (first use in this function)

Cpufreq: prevent negative px resident time, add spinlock to avoid race Due to NOW() value may drift between different cpus, we add protection to prevent negative px resident time. Due to both cpufreq logic and xenpm may race accessing cpufreq_statistic_data, we add spinlock to avoid race. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> _______________________________________________

Hi, When I tested pvfb, I got the following warnings. It seems to be caused by checking/setting info->dirty without dirty_lock. We need to check/set info->dirty safely. xenfb_update_screen bogus rect 2147483647 0 2147483647 0 BUG: warning at /root/linux-2.6.18-xen.hg/drivers/xen/fbfront/xenfb.c:240/xenfb_update_screen() Call Trace: [<ffffffff8036920e>] xenfb_thread+0x19b/0x2be

Hi, i read the xenpm wiki page, but i cannot use the "p-states". xenpm shows: xenpm cpu id : 0 total C-states : 2 idle time(ms) : 1776034 C0 : transition [00000000000000000000] residency [00000000000000000000 ms] C1 : transition [00000000000000260278] residency

Akio, Thank you for pointing out this issue. Maybe I sent out the older one incorrectly.:( Thanks again. -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com] > Sent: 2006年7月26日 19:24 > To: Zhang, Xiantao; xen-devel@lists.xensource.com > Cc: xen-ia64-devel@lists.xensource.com > Subject: Re: [Xen-ia64-devel]

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

I do not seem to be able to get any where with the power management functions. I have had a look at the xenpm Wiki page, but it hasn''t helped. Its probably something completely obvious, but I can''t see it. I running Xen 3.4.0 on Centos 5.3 x86_64 using the gitco RPMs on an Intel S5000PSL motherboard with 2 x Xeon 5410s. Dom0 is running the latest Centos 5.3 kernel. My xm

Hi, This patch re-enables --all option of xenctx on x86. Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Best Regards, Akio Takebe _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, xentrace_format cannot use "0x016x" format as we expect. It show only %(N) as "0x016x" format, not as "%(N+1)08x%(N)08x". So I fixed tools/xentrace/formats by using "%(N+1)08x%(N)08x" format. Also I added some TRC_PV entries. Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Best Regards, Akio Takebe

Hi, We found a bug that rombios cannot get the correct BDF during rom_scan. This patch fixes rombios to get the BDF for calling INIT function. I''m sorry for the inconvenience. m(__)m Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Signed-off-by: Kouya Shimura <kouya@jp.fujitsu.com> Best Regards, Akio Takebe _______________________________________________

I am seeing random reboots after installing Xen 3.2.1 (running with linux-2.6.18-8 pulled from a few days ago). So far, the reboots only happen if I have enabled cpufreq=dom0-kernel and actually run frequency scaling (such as with the ondemand governor). The reboots only happen after a few hours. The machines seem to be stable if I pass the cpufreq option to Xen but disable frequency scaling. I

Currently cpufreq and xenpm are out of sync. Fix cpufreq reporting of if turbo mode is enabled or not. Fix xenpm to not decode for tristate, but a boolean. Signed-off-by: Jacob Shin <jacob.shin@amd.com> --- tools/misc/xenpm.c | 14 +++----------- xen/drivers/cpufreq/utility.c | 2 +- 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/tools/misc/xenpm.c

Hi, Jeremy Since now the pv_ops domain0 is approaching, we are considering to port the dom0 power management related code, or more specifically, the Cx/Px ACPI info parsing code, to pv_ops domain0 tree, so that people can utilize Xen power management capability (Cx/PX) under pv_ops domain0. This RFC is a draft version for comments. === Overview === Requirement: Xen hypervisor need Cx/Px ACPI

Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).