similar to: [PATCH] xenpm: Fix reporting of C0 residence times

- use consistent error values (stop mixing of [positive] errno values with literal -E... ones) - properly format output - don''t use leading zeros in decimal output - move printing of average frequency into P-state conditional (rather than a C-state one) - don''t print some C-state related info when CPU idle management is disabled in the hypervisor - use calloc() for array

x86 pm : provide CC7/PC2 residency Sandy bridge introduces new MSR to get cc7/pc2 residency (core C-state 7/package C-state 2). Print the cc7/pc2 residency when on sandy bridge platform. Signed-off-by: Yang Zhang <yang.z.zhang@intel.com> diff -r 662dbf6ee71c tools/libxc/xc_pm.c --- a/tools/libxc/xc_pm.c Mon Oct 24 18:01:07 2011 +0100 +++ b/tools/libxc/xc_pm.c Fri Oct 28

Hi Nouveau enthusiasts, One week ago was merged the thermal/fan management code for most nvidia cards. So far, no major issue arose but we would like to have more testing as soon as possible to deliver a nice and solid support when Linux 3.8 is released. Thermal management is split into two parts: - Temperature monitoring: Making sure your card doesn't overheat - Fan management: Driving

Hi, I wrote a patch for nouveau_backlight.c to support the backlight control of the GT 525M. Only the case NV_C0: is needed to get the backlight control with my NVC0 card working. I don't think that it's worth to add new functions for c0 if the old ones still work. This is my first patch for the Linux kernel. Best Regards Florian Scholz -------------- next part -------------- A

Probably missing something obvious here, but what determines when an RPM is built with a .c0 extension vs. not? Seems to be mostly on kernel RPM's. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20050122/12adf421/attachment-0003.html>

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

Does anyone know what is the latest version of dom0-kernel, that supports fully xenpm hypercalls? I tried from 3.0 to 3.3 with xen-4.1.3, but none of them has xenpm working. On the other hand native kernel cpufreq is OK with all of them. My CPU is Xeon family 6 on PowerEdge 1950 III box. Regards, Dimitar Kazakov

Does anyone know what is the latest version of dom0-kernel, that supports fully xenpm hypercalls? I tried from 3.0 to 3.3 with xen-4.1.3, but none of them has xenpm working. On the other hand native kernel cpufreq is OK with all of them. My CPU is Xeon family 6 on PowerEdge 1950 III box. Regards, Dimitar Kazakov

Hi, All, I have some problem of using dvfs in Xen 3.4.1 and 2.6.18 kernel. I enabled Speed option in BIOS and add "cpufreq=xen" in the grub file. But when I entered my dom0 and type "xenpm get-cpufreq-XXX" (any xenpm argument), it returns "[CPU0] failed to get CPU P state". I am wondering if I should enable some feature of 2.6.18 during the kernel configuration.

Hi, All, I have some problem of using dvfs in Xen 3.4.1 and 2.6.18 kernel. I enabled Speed option in BIOS and add "cpufreq=xen" in the grub file. But when I entered my dom0 and type "xenpm get-cpufreq-XXX" (any xenpm argument), it returns "[CPU0] failed to get CPU P state". I am wondering if I should enable some feature of 2.6.18 during the kernel configuration.

Specifically, what values are or aren''t accepted as CPU identifier, and how the values get interpreted should be consistent across sub-commands (intended behavior now: non-negative values are okay, and along with omitting the argument, specifying "all" will also be accepted). For error handling, error messages should get consistently issued to stderr, and the tool should now

Hi, I need a help with tracking down following issue: When trying to boot Xen on a system with Ivy Bridge stepping C0 CPU, it is stuck on CPU initialization. I''ve added some tracing to apic writes/reads and traced it so far to sending INIT IPI. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Setting warm reset code and vector. (XEN) apic_wrmsr (0x280,0x0)

Hi, I'm trying to get standard errors for some of the variables in my data frame. One of the questions on my survey is whether faculty coordinate across curriculum to include Arts Education as subject matter. All the responses are coded in zeros and ones obviously. For some of the other variables I have a 2 for those that responded with "Don't Know". I'm getting NA for

Source: xen Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important - x86: Make asmlinkage explicitly a no-op, and avoid usage in arch/x86 Build-fix, done different in Debian. - tools/ocaml: Fix 2 bit-twiddling bugs and an off-by-one Relevant for xcp. - x86_64: Fix off-by-one error setting up the Interrupt Stack Tables Hypervisor code running with wrong stack. Breaks error handling

On Sun, Feb 20, 2005 at 08:15:42PM +0000, Karl Heyes wrote: > setting <logsize> will cause an automatic log rotation when a certain > file size has been reached. It renames <logfile> to <logfile>.1 then > opens a new file <logfile> Since all my other logs are rotated on a daily/weekly basis, I want my ices logs to behave in the same way. Nevertheless, this thread

A new intel-gpu-tools quarterly release is available with the following changes: - Various new tests and tools - Single combined test list (supported by piglit since commit 8a122bb) - Optional dependency on libunwind to provide automatic stack traces on test failures. (Thomas Wood) - Add optional default debug and optimisation flags for tests to enable better stack traces and debugging.

i can do it, but i mean it would not talk much to you ; ) [2003-05-31 12:00:25] INFO ices-core/main ices started... [2003-05-31 12:00:25] EROR stream/ices_instance_stream libshout error: Out of memory [2003-05-31 12:00:31] INFO signals/signal_int_handler Shutdown requested... [2003-05-31 12:16:47] INFO ices-core/main ices started... [2003-05-31 12:16:47] EROR stream/ices_instance_stream

I just built icecast and ices from CVS source. The compile went fine. But I'm having trouble connecting to the server and hearing anything. In one shell, I start icecast with: src/icecast -c conf/icecast.xml That appears to start things off fine. Then in another shell, I start ices: src/ices conf/ices-playlist.xml At this point, icecast prints some text: connection added.... DEBUG: source

Karl, I installed icecast/ices from the latest stable ebuild on gentoo portage. It appears from the log file that ices is only version 2.0.0 even though the ebuild is version 2.1.0. I just reinstalled icecast with the newest (unstable) ebuild and it still doesn't seem to have version 2.0.1 of ices. Do you recommend that I manually compile or that I find a way to use a wrapper for ALSA to