search for: cpu_idle

...core is taken off-line it is placed in C1 state (unless MONITOR/MWAIT is used). This patch allows a core to go to deeper C states resulting in significantly higher power savings. Signed-off-by: Boris Ostrovsky <boris.ostrovsky@amd.com> diff -r a7bacdc5449a -r 99df5c6b2964 xen/arch/x86/acpi/cpu_idle.c --- a/xen/arch/x86/acpi/cpu_idle.c Mon Feb 27 17:05:18 2012 +0000 +++ b/xen/arch/x86/acpi/cpu_idle.c Thu Mar 01 23:52:41 2012 +0100 @@ -566,6 +566,7 @@ static void acpi_dead_idle(void) struct acpi_processor_power *power; struct acpi_processor_cx *cx; void *mwait_ptr; + struct cp...

...not control the number of entries in the ACPI tables, and is required to pass everything it finds to Xen, reduce the ERR to an INFO. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> CC: Keir Fraser <keir@xen.org> CC: Jan Beulich <JBeulich@suse.com> --- xen/arch/x86/acpi/cpu_idle.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/arch/x86/acpi/cpu_idle.c b/xen/arch/x86/acpi/cpu_idle.c index 8cb1514..90e0a49 100644 --- a/xen/arch/x86/acpi/cpu_idle.c +++ b/xen/arch/x86/acpi/cpu_idle.c @@ -1031,7 +1031,7 @@ long set_cx_pminfo(uint32_t cpu, struct xen_...

...000000000046 R11: 0000000000000046 R12: 0000000000000000 R13: ffff81063e480000 R14: 0000000000000000 R15: 0000000000000000 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 --- <exception stack> --- #3 [ffffffff803f1f48] acpi_processor_idle at ffffffff8019765e #4 [ffffffff803f1f90] cpu_idle at ffffffff8004939e PID: 0 TASK: ffff810115f11100 CPU: 1 COMMAND: "swapper" #0 [ffff810115f38f20] crash_nmi_callback at ffffffff8007a3bf #1 [ffff810115f38f40] do_nmi at ffffffff8006585a #2 [ffff810115f38f50] nmi at ffffffff80064ebf [exception RIP: acpi_processor_idle+579]...

.../37] do_IRQ+0x1f/0x25 Dec 8 12:19:27 server kernel: [evtchn_do_upcall+132/192] evtchn_do_upcall+0x84/0xc0 Dec 8 12:19:27 server kernel: [hypervisor_callback+44/52] hypervisor_callback+0x2c/0x34 Dec 8 12:19:27 server kernel: [xen_idle+97/127] xen_idle+0x61/0x7f Dec 8 12:19:27 server kernel: [cpu_idle+76/97] cpu_idle+0x4c/0x61 Dec 8 12:19:27 server kernel: [start_kernel+370/372] start_kernel+0x172/0x174 Dec 8 12:19:27 server kernel: Mem-info: Dec 8 12:19:27 server kernel: DMA per-cpu: Dec 8 12:19:27 server kernel: cpu 0 hot: high 90, batch 15 used:14 Dec 8 12:19:27 server kernel: cpu 0 col...

...e, there will be another #PF. These series of #PF produce a dead lock around tasklet_lock. This patch avoids using per_cpu variable inside play_dead. Signed-off-by: Shan Haitao <haitao.shan@intel.com> Signed-off-by: Wei Gang <gang.wei@intel.com> diff -r dac86c85222e xen/arch/x86/acpi/cpu_idle.c --- a/xen/arch/x86/acpi/cpu_idle.c Fri Feb 18 19:07:11 2011 +0000 +++ b/xen/arch/x86/acpi/cpu_idle.c Wed Feb 23 17:05:32 2011 +0800 @@ -569,7 +569,8 @@ static void acpi_dead_idle(void) { case ACPI_CSTATE_EM_FFH: /* Not treat interrupt as break event */ -...

When I came into work this morning the console had the following: bio_endio __end_that_request_first scsi_end_request scsi_io_completion scsi_finish_command scsi_softirq __do_softirq do_softirg do_irq command_interrupt default_idle cpu_idle start_kernel Panic I am running software RAID-1 on this machine. I had 2 IDE disks and the machine when down once in a while with similiar messages. I switched to brand new 300 GIG SATA drives and now I am seeing the same kernel panic. What might be the problem here? THanks for any suggestions....

Hi , I have two KVM guests in ubuntu host machine.I am using Python binding of Libvirt API to query on the hypervisor and capture the CPU , memory related information of the guest machines. I need to capture the detail information regarding CPU like : cpu_aidle, cpu_idle, cpu_speed, cpu_wio and memory like :mem_cached,mem_buffers,mem_free etc. of the guest machines. How could I get these information? Please help me. Thanks in Advance!! Arpita -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/l...

...<c0123315>] __do_softirq+0x70/0xdb [<c01233bb>] do_softirq+0x3b/0x42 [<c0111cda>] smp_apic_timer_interrupt+0x9c/0xb2 [<c0104373>] apic_timer_interrupt+0x1f/0x24 [<c0101cc3>] mwait_idle_with_hints+0x3b/0x3f [<c0101cd3>] mwait_idle+0xc/0x1b [<c010271c>] cpu_idle+0x63/0x79 ======================= BUG: soft lockup detected on CPU#2! [<c013c890>] softlockup_tick+0x93/0xc2 [<c0127585>] update_process_times+0x26/0x5c [<c0111cd5>] smp_apic_timer_interrupt+0x97/0xb2 [<c0104373>] apic_timer_interrupt+0x1f/0x24 [<c01c007b>] blk_d...

...- turn off arbitration disabling only when the first CPU leaves C3 (paralleling how arbitration disabling gets turned on) - only set the (global) bus master reload flag once (when the first target CPU gets processed) Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/acpi/cpu_idle.c +++ b/xen/arch/x86/acpi/cpu_idle.c @@ -439,8 +439,8 @@ static void acpi_processor_idle(void) (next_state = cpuidle_current_governor->select(power)) > 0 ) { cx = &power->states[next_state]; - if ( power->flags.bm_check && acpi_idle_bm_check()...

It has never been used for anything, and Linux 3.7 doesn''t propagate this information anymore. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- Konrad, on the pv-ops side it may be better to pass zero rather than leaving the field completely uninitialized. --- a/xen/arch/x86/acpi/cpu_idle.c +++ b/xen/arch/x86/acpi/cpu_idle.c @@ -935,7 +935,6 @@ static void set_cx( } cx->latency = xen_cx->latency; - cx->power = xen_cx->power; cx->target_residency = cx->latency * latency_factor; if ( cx->type == ACPI_STATE_C1 || cx->type == AC...

...he lock struct: @ ffff8800020e2480: 2f102e70 0000000c 00000002 00000000 so slock is: 2f102e70 The remaining vcpus are idling: ffffffff800083aa: 0:hypercall_page+3aa pop %r11 ffffffff8000f0c7: 0:xen_safe_halt+f7 addq $0x18, %rsp ffffffff8000a5c5: 0:cpu_idle+65 jmp 0:cpu_idle+4e ffffffff803558fe: 0:cpu_bringup_and_idle+e leave But the baffling thing is the vcpu upcall mask is set. The block schedop call does local_event_delivery_enable() first thing, so the mask should be clear!!! Another baffling thing is...

Hi Konrad I encountered a bug when trying to bring offline a cpu then online it again in HVM. As I''m not very familiar with HVM stuffs I cannot come up with a quick fix. The HVM DomU is configured with 4 vcpus. After booting into command prompt, I do following operations. # echo 0 > /sys/devices/system/cpu/cpu3/online # echo 1 > /sys/devices/system/cpu/cpu3/online With

What is the point of specifying "current" as the address to monitor? The memory location of interest really is irq_stat[cpu].__softirq_pending, and if that was used it would then also be possible to actually avoid sending IPIs when monitor/mwait are in use, as is being done on Linux. Jan _______________________________________________ Xen-devel mailing list

...nd[j].cc7 - cxstat_start[j].cc7; + printf("\t\tCC7\t%"PRIu64" ms\t%.2f%%\n", res / 1000000UL, + 100UL * res / (double)sum_cx[j]); printf("\n"); } diff -r 662dbf6ee71c xen/arch/x86/acpi/cpu_idle.c --- a/xen/arch/x86/acpi/cpu_idle.c Mon Oct 24 18:01:07 2011 +0100 +++ b/xen/arch/x86/acpi/cpu_idle.c Fri Oct 28 21:33:07 2011 +0800 @@ -60,11 +60,13 @@ #define GET_HW_RES_IN_NS(msr, val) \ do { rdmsrl(msr, val); val = tsc_ticks2ns(val); } while( 0 ) +#define GET_PC2_RES(val) GET...

...master kernel: [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 Apr 18 01:10:00 xenmaster kernel: [<ffffffff8026e4e5>] raw_safe_halt+0x84/0xa8 Apr 18 01:10:00 xenmaster kernel: [<ffffffff8026ba22>] xen_idle+0x38/0x4a Apr 18 01:10:00 xenmaster kernel: [<ffffffff8024a803>] cpu_idle+0x97/0xba Apr 18 01:10:00 xenmaster kernel: [<ffffffff80634b09>] start_kernel+0x21f/0x224 Apr 18 01:10:00 xenmaster kernel: [<ffffffff806341e5>] _sinittext+0x1e5/0x1eb Apr 18 01:10:00 xenmaster kernel: Apr 18 01:10:00 xenmaster kernel: BUG: warning at drivers/ata/libata-core.c:4923/at...

Just gave 3.0 a spin. Had been running 2.0.7 for the past 3 months or so without problems (aside from intermittent failure during live migration). Anyway, 3.0 seems to have an issue with my machine. It starts up the 4 domains that I''ve got defined (was running 6 user domains with 2.0.7, but two of those were running 2.4 kernels which I can''t seem to build with Xen 3.0 yet, and

...execution right after VCPUOP_down hypercall. That was OK (albeit the API for play_dead assumes that the CPU stays dead and never returns) but with commit 4b0c0f294 (tick: Cleanup NOHZ per cpu data on cpu down) that is no longer safe as said commit resets the ts->inidle which at the start of the cpu_idle loop was set. The net effect is that we get this warn: Broke affinity for irq 16 installing Xen timer for CPU 1 cpu 1 spinlock event irq 48 ------------[ cut here ]------------ WARNING: at /home/konrad/linux-linus/kernel/time/tick-sched.c:935 tick_nohz_idle_exit+0x195/0x1b0() Modules linked in: d...

...<4> [<0000000000466556>] vring_interrupt+0x72/0x88 <4> [<00000000004801a0>] kvm_extint_handler+0x34/0x44 <4> [<000000000010d22c>] do_extint+0xbc/0xf8 <4> [<0000000000113f98>] ext_no_vtime+0x16/0x1a <4> [<000000000010a182>] cpu_idle+0x216/0x238 <4>([<000000000010a162>] cpu_idle+0x1f6/0x238) <4> [<0000000000568656>] rest_init+0xaa/0xb8 <4> [<000000000084ee2c>] start_kernel+0x3fc/0x490 <4> [<0000000000100020>] _stext+0x20/0x80 <4> <4> <0>Ke...

...<4> [<0000000000466556>] vring_interrupt+0x72/0x88 <4> [<00000000004801a0>] kvm_extint_handler+0x34/0x44 <4> [<000000000010d22c>] do_extint+0xbc/0xf8 <4> [<0000000000113f98>] ext_no_vtime+0x16/0x1a <4> [<000000000010a182>] cpu_idle+0x216/0x238 <4>([<000000000010a162>] cpu_idle+0x1f6/0x238) <4> [<0000000000568656>] rest_init+0xaa/0xb8 <4> [<000000000084ee2c>] start_kernel+0x3fc/0x490 <4> [<0000000000100020>] _stext+0x20/0x80 <4> <4> <0>Ke...

Hi, I just want to know if somebody use 2.6.31.4 xenified kernel (aka OpenSUSE) in production? We have been testing it on new Nehalem Xeon server for few weeks w/o any problem. But as soon we tried it on production machine - after several production domUs started - hard OS failure. We had to switch back to 2.6.18.8 - xen stock kernel. Peter _______________________________________________