search for: _pct

...) { assign(paste("x",i,sep=""),subset(dt,grp==i)) df<-eval(parse(text=paste("x",i,sep=""))) yy <- freqtot(df,cat1); names(yy)<-c("Group",paste("grp_",i,"_cnt",sep=""),paste("grp_",i,"_pct",sep="")) xx<-merge(xx,yy,by.x="Group",all=TRUE) } print(xx) } The output is > xyz <- freqgrp(dt,cat1,ind,2) Group cnt pct grp_1_cnt grp_1_pct grp_2_cnt grp_2_pct 1 0 38 76 23 100 15 55.6 2 1 12 24 NA NA...

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

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

There''re basically two methods to enter a given C-state: legacy (hlt + I/O read), and native(using mwait). MWAIT is always preferred when both underlying CPU and OS support, which is a more efficient way to conduct C-state transition. Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one step to notify BIOS about a set of capabilities supported by OSPM. One capability

...afec000 0000: 53 53 44 54 3e 07 00 00 01 71 50 6d 52 65 66 00 SSDT>....qPmRef. 0010: 43 70 75 30 49 73 74 00 00 30 00 00 49 4e 54 4c Cpu0Ist..0..INTL 0020: 09 11 06 20 10 49 71 5c 2e 5f 50 52 5f 43 50 55 ... .Iq\._PR_CPU 0030: 30 08 5f 50 50 43 00 14 44 07 5f 50 43 54 00 a0 0._PPC..D._PCT.. 0040: 3e 90 7b 43 46 47 44 01 00 7b 50 44 43 30 01 00 >.{CFGD..{PDC0.. 0050: a4 12 2c 02 11 14 0a 11 82 0c 00 7f 00 00 00 00 ..,............. 0060: 00 00 00 00 00 00 00 79 00 11 14 0a 11 82 0c 00 .......y........ 0070: 7f 00 00 00 00 00 00 00 00 00 00 00 79 00 a4 12 ............y.....