search for: timer_softirq_action

...ng the reboot. Details: dom0 will also reboot with the following console messages: (XEN) HVM_PIT: guest freq in cycles=3002234 (XEN) CPU: -14688196 (XEN) EI…N…þÅÿì1ÿN(XEN) CPU: 12 (XEN) EIP: e008:[<ff117988>]CPU: 9 (XEN) EIP: e008:[<ff111584>]CPU: 4 (XEN) EIP: e008:[<ff111584>] timer_softirq_action+0x64/0x140 (XEN) EFLAGS: 00010006 CONTEXT: hypervisor (XEN) eax: 0dee319b ebx: ffff4d85 ecx: 00000000 edx: 000000c0 (XEN) esi: ff1e9a00 edi: 00000480 ebp: ffbd2080 esp: ffbd1f68 (XEN) cr0: 8005003b cr3: 00178000 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from...

Keir, this change looks a little odd to me - the code as it was before already set the timeout to jiffies + 1 as the lowest possible value. So I don''t understand how you could have observed any spinning over more than really short periods of time (where you happen to just see jiffies increment while setting the timeout). I''d therefore appreciate any insight to the background of

...000e033 0000000000000246 ffff8801d9c29dc8 000000000000e02b (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffff8300d78aa000 (XEN) Xen call trace: (XEN) [<ffff82c48011f55c>] remove_from_heap+0x8f/0xd0 (XEN) [<ffff82c48011fa56>] timer_softirq_action+0x175/0x3a9 (XEN) [<ffff82c48011d921>] do_softirq+0x6f/0x8e (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) FATAL TRAP: vector = 2 (nmi) (XEN) [error_code=0000] , IN INTERRUPT CONTEXT (XEN) **************************************** (XEN) (XEN) Reboot i...

...(XEN) [<ff12ab6b>] do_IRQ+0xe8/0x299 (XEN) [<ff1267e6>] common_interrupt+0x56/0x60 (XEN) [<ff11fa41>] printk+0x15d/0x164 (XEN) [<ff16e2c9>] hvm_dpci_eoi+0xd9/0x117 (XEN) [<ff16e348>] pt_irq_time_out+0x41/0x47 (XEN) [<ff117aba>] timer_softirq_action+0xaf/0x12f (XEN) [<ff116919>] do_softirq+0x4f/0x66 (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Assertion ''(sp == 0) || (peoi[sp-1].vector < vector)'' failed at irq.c:226 (XEN) ***************************...

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

...call trace: (XEN) [<ffff82d0801285f7>] check_lock+0x37/0x3b (XEN) [<ffff82d0801286ec>] _spin_lock_irqsave+0x17/0x84 (XEN) [<ffff82d08016a575>] irq_guest_eoi_timer_fn+0x27/0x150 (XEN) [<ffff82d08012b225>] execute_timer+0x47/0x62 (XEN) [<ffff82d08012b323>] timer_softirq_action+0xe3/0x215 (XEN) [<ffff82d080128019>] __do_softirq+0x81/0x8c (XEN) [<ffff82d080128072>] do_softirq+0x13/0x15 (XEN) [<ffff82d08015ca75>] idle_loop+0x67/0x77 (XEN) (XEN) Xen BUG at spinlock.c:48 (XEN) (XEN) **************************************** (XEN) ----[ Xen-4.4-unst...

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have