search for: xen_hypercall_sched_op

...lete_done+0x6a/0xb0 igb_poll+0x38d/0x720 [igb] ? igb_msix_ring+0x2e/0x40 [igb] ? __handle_irq_event_percpu+0x4b/0x1a0 net_rx_action+0x158/0x360 __do_softirq+0xd1/0x283 irq_exit+0xe9/0x100 xen_evtchn_do_upcall+0x35/0x50 xen_do_hypervisor_callback+0x1e/0x40 <EOI> ? xen_hypercall_sched_op+0xa/0x20 ? xen_hypercall_sched_op+0xa/0x20 ? xen_safe_halt+0x10/0x20 ? default_idle+0x1e/0xd0 ? arch_cpu_idle+0xf/0x20 ? default_idle_call+0x2c/0x40 ? cpu_startup_entry+0x1ac/0x240 ? rest_init+0x77/0x80 ? start_kernel+0x4a7/0x4b4 ? set_init_arg+0x55/0x55 ? x86_64_start...

I am working on some other bugs and perf issues - and while working I noticed that both sparse and Coverity have reported some issues with Xen drivers. Please see attached various bug-fixes that I am proposing for 3.6.

...c2>] net_rx_action+0x112/0x2a0 [<ffffffff81076b7c>] __do_softirq+0xfc/0x2b0 [<ffffffff81076e3d>] irq_exit+0xbd/0xd0 [<ffffffff813b2cbc>] xen_evtchn_do_upcall+0x3c/0x50 [<ffffffff8167659e>] xen_do_hypervisor_callback+0x1e/0x40 <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff8100a830>] ? xen_safe_halt+0x10/0x20 [<ffffffff8101ec84>] ? default_idle+0x24/0xc0 [<ffffffff8101e28f>] ? arch_cpu_idle+0xf/0x20 [<ffffffff810b2276>] ? cpuidle_idle_call+0xd6/0x1d0 [<fff...

...tirq+0x65/0xa0 > >> [<ffffffff8107656b>] irq_exit+0xab/0xc0 > >> [<ffffffff812f97d5>] xen_evtchn_do_upcall+0x35/0x50 > >> [<ffffffff81511d8e>] xen_do_hypervisor_callback+0x1e/0x30 > >> <EOI> > >> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 > >> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 > >> [<ffffffff8100a0b0>] ? xen_safe_halt+0x10/0x20 > >> [<ffffffff8101dfeb>] ? default_idle+0x5b/0x170 > >> [<ffffffff81014ac6>] ? cpu_idle+0xc6/0xf0 > >>...

...0x90 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff813a0d67>] xen_evtchn_do_upcall+0x37/0x50 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff8165c05e>] xen_do_hypervisor_callback+0x1e/0x40 Jul 03 11:31:23 antares.fsoft.nnet kernel: <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff8100b330>] ? xen_safe_halt+0x10/0x20 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff8101ea94>] ? default_idle+0x...

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

...Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff813a0d67>] xen_evtchn_do_upcall+0x37/0x50 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8165c05e>] xen_do_hypervisor_callback+0x1e/0x40 Jul 03 11:31:23 myDom0.mynetwork.net kernel: <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8100b330>] ? xen_safe_halt+0x10/0x20 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff8101ea94>] ? default_i...

...290 [ 4.355153] [<ffffffff8106c965>] ? irq_exit+0x95/0xa0 [ 4.355244] [<ffffffff813579b5>] ? xen_evtchn_do_upcall+0x35/0x50 [ 4.355352] [<ffffffff815113de>] ? xen_do_hypervisor_callback+0x1e/0x30 [ 4.355467] <EOI> [ 4.355501] [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [ 4.355619] [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [ 4.355728] [<ffffffff81009e0c>] ? xen_safe_halt+0xc/0x20 [ 4.355824] [<ffffffff8101c949>] ? default_idle+0x19/0xb0 [ 4.355920] [<ffffffff810a7dc0>] ? cpu_startup_entry+0x340/0x400 [...

Hi everyone, I would like to ask what the current status of FLR, or better of FLR emulation is in latest Xen and if we can expect better support in the future. I''m asking because with xl (latest build and traditional qemu, not upstream), I always had problems with rebooting domUs which have vga cards passed through to them, because appearently they don''t get reinitialized and

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

N.B. Sorry for the duplicate. This patch series were resent as the original one was rejected by the vger.kernel.org list server due to long header. There is no change in content. v7->v8: - Remove one unneeded atomic operation from the slowpath, thus improving performance. - Simplify some of the codes and add more comments. - Test for X86_FEATURE_HYPERVISOR CPU feature bit

N.B. Sorry for the duplicate. This patch series were resent as the original one was rejected by the vger.kernel.org list server due to long header. There is no change in content. v7->v8: - Remove one unneeded atomic operation from the slowpath, thus improving performance. - Simplify some of the codes and add more comments. - Test for X86_FEATURE_HYPERVISOR CPU feature bit

We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment