similar to: Xen 4.2.0 - CPU Frequency Scaling

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

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

I've been playing and comparing frequency scaling between AMD and Intel CPUs yesterday and there seem to be great differences between AMD and Intel and some gotchas. This is all on CentOS 5.2 with latest Xen kernels (which are supposed to be powersaving-enabled since 5.2). AMD: It seems once I get the AMD CPU to use the ondemand governor it works very well and very efficiently. But this

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

Hi, The default "stop" action for the cpupower service seems to be to set the ondemand governor, but this fails. I can reproduce the issue directly by running cpupower: $ sudo cpupower frequency-set -g ondemand Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? -

Another bundle of issues from Coverity triage. The first one is in x86/mm, and looks scarier than it is. The others are all in xen/drivers and AFAICT are pretty minor. Cheers, Tim.

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

On 03/25/2015 03:47 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 16, 2015 at 02:16:13PM +0100, Peter Zijlstra wrote: >> Hi Waiman, >> >> As promised; here is the paravirt stuff I did during the trip to BOS last week. >> >> All the !paravirt patches are more or less the same as before (the only real >> change is the copyright lines in the first patch).

On 03/25/2015 03:47 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 16, 2015 at 02:16:13PM +0100, Peter Zijlstra wrote: >> Hi Waiman, >> >> As promised; here is the paravirt stuff I did during the trip to BOS last week. >> >> All the !paravirt patches are more or less the same as before (the only real >> change is the copyright lines in the first patch).

struct cpufreq_policy, including a cpumask_t member, gets copied in cpufreq_limit_change(), cpufreq_add_cpu(), set_cpufreq_gov(), and set_cpufreq_para(). Make the member a cpumask_var_t, thus reducing the amount of data needing copying (particularly with large NR_CPUS). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- 2011-09-20.orig/xen/arch/x86/acpi/cpufreq/cpufreq.c 2011-10-12

Add cpufreq governors: performance, powersave, userspace This patch add 3 more governors beside original running ondemand cpufreq governor. performance governor is with best performance, keeping cpu always running at highest freq; powersave governor is with best power save effect, keeping cpu always running at lowest freq; userspace governor provide user setting freq ability; Signed-off-by: Liu,

This creates filesystems on demand. A client simply connects with a desired export name and a new export is created. The export is persistent (until deleted by the server admin), and clients may disconnect and reconnect. In some respects this is similar to the nbdkit-tmpdisk-plugin, or nbdkit-file-plugin with the dir= option. --- plugins/ondemand/nbdkit-ondemand-plugin.pod | 190 ++++++

Speex 1.0 - in file sb_celp.c line 218 change speex_decoder_ctl(...) to speex_encoder_ctl(...): void *sb_encoder_init(SpeexMode *m) { . . . --> speex_decoder_ctl(st->st_low, SPEEX_GET_SAMPLING_RATE, &st->sampling_rate); // Replace <-- speex_encoder_ctl(st->st_low, SPEEX_GET_SAMPLING_RATE, &st->sampling_rate); st->sampling_rate*=2; return st; } --

Hi, No, it only happens with speex_wb_mode. But like I said, it is because in wideband mode, the function sb_encoder_init is called and this function initializes the sampling rate using speex_*de*coder_ctl instead of speex_*en*coder_ctl In narrowband mode, the sampling rate is just initialized to 8000 st->sampling_rate=8000; BTW, I saw that my email was added to an existing thread instead of

During the 1.21 development cycle we added support for listing exports. However at the time that 1.22 was released we did not feel the API was sufficiently finalized to commit to in a stable branch. Therefore this new API was removed before 1.22 was released, but the feature continues to be developed upstream and should appear in nbdkit 1.24. Note this also hides the nbdkit*export* functions so

Hi, I'm using speex 1.1.4 and when I query SPEEX_GET_SAMPLING_RATE as in speex_encoder_ctl ( m_pEncoderState, SPEEX_GET_SAMPLING_RATE, &m_SampleRate ); I get 2 The encoder is initialized with m_pEncoderState = speex_encoder_init ( &speex_wb_mode ); On the decoder side, the correct sampling rate is returned: m_pDecoderState = speex_decoder_init ( &speex_wb_mode );

Hi! A note on style: Looking at this chunk of the patch -- @@ -382,9 +382,15 @@ int main(int argc, char *argv[]) frame_size = sampling_rate/25; else if (strcmp(argv[ args + 1 ], "60")==0) frame_size = 3*sampling_rate/50; + else if (strcmp(argv[ args + 1 ], "80")==0) + frame_size = 4*sampling_rate/50; +

Hi, Do you get that problem with speex_nb_mode too (or only speex_wb_mode)? Jean-Marc Le lun 29/03/2004 à 05:35, Chris Flerackers a écrit : > Hi, > > I'm using speex 1.1.4 and when I query SPEEX_GET_SAMPLING_RATE > as in > speex_encoder_ctl ( m_pEncoderState, SPEEX_GET_SAMPLING_RATE, > &m_SampleRate ); > I get > 2 > The encoder is initialized with

On 8/14/20 12:20 PM, Richard W.M. Jones wrote: > This creates filesystems on demand. A client simply connects with a > desired export name and a new export is created. The export is > persistent (until deleted by the server admin), and clients may > disconnect and reconnect. In some respects this is similar to the > nbdkit-tmpdisk-plugin, or nbdkit-file-plugin with the dir=