search for: cpu_down

.../0x200  [<c0105810>] die+0x100/0x1a0  [<c01156f6>] do_page_fault+0x3c6/0x8b1  [<c0105067>] error_code+0x2b/0x30  [<c010e3ba>] cache_remove_dev+0x2a/0x60  [<c010e425>] cacheinfo_cpu_callback+0x35/0x40  [<c012fae8>] notifier_call_chain+0x18/0x40  [<c013b889>] cpu_down+0x139/0x260  [<c028bc9f>] smp_suspend+0x7f/0x100  [<c028ca80>] __do_suspend+0x40/0x180  [<c0136a06>] kthread+0x96/0xe0  [<c0102e95>] kernel_thread_helper+0x5/0x10 Code: 0c 5b 5e 5f 5d c3 8d 74 26 00 8d bc 27 00 00 00 00 55 89 e5 57 56 89 d6 53 89 c3 8d 04 92 8b 14 9d 20 4d 4...

I'm sending a first draft of my proposed cpu hotplug driver for kvm/virtio The first patch is the kernel module, while the second, the userspace pci device. The host boots with the maximum cpus it should ever use, through the -smp parameter. Due to real machine constraints (which qemu copies), i386 does not allow for any addition of cpus after boot, so this is the most general way. I do

I'm sending a first draft of my proposed cpu hotplug driver for kvm/virtio The first patch is the kernel module, while the second, the userspace pci device. The host boots with the maximum cpus it should ever use, through the -smp parameter. Due to real machine constraints (which qemu copies), i386 does not allow for any addition of cpus after boot, so this is the most general way. I do

Is there any real user for this vIRQ? I''m asking because, while debugging a problem that required to add some printk()s that could temporarily issue at a high rate, I ran into the situation that this extra output prevented guest/dom0 boot from making any progress. As I then realized this was due to the tasklet_schedule() called from inside the console handling code, which resulted in

Is there any real user for this vIRQ? I''m asking because, while debugging a problem that required to add some printk()s that could temporarily issue at a high rate, I ran into the situation that this extra output prevented guest/dom0 boot from making any progress. As I then realized this was due to the tasklet_schedule() called from inside the console handling code, which resulted in

...7 +1522,6 @@ static struct hvm_function_table __read_ .inject_trap = vmx_inject_trap, .init_hypercall_page = vmx_init_hypercall_page, .event_pending = vmx_event_pending, - .do_pmu_interrupt = vmx_do_pmu_interrupt, .cpu_up = vmx_cpu_up, .cpu_down = vmx_cpu_down, .cpuid_intercept = vmx_cpuid_intercept, @@ -1642,7 +1636,7 @@ static void vmx_cpuid_intercept( { case 0x80000001: /* SYSCALL is visible iff running in long mode. */ - hvm_get_segment_register(v, x86_seg_cs, &cs); +...

The attached patch: 1. Converts the shutdown driver and xend to use the store instead of control messages, 2. Includes Anthony''s xenstore notification code, and 3. Changes xend so that sysrq''s are no longer sent as "special case" shutdown messages. Store keys are cheap, so making the sysrq delivery less obscure is good. I think I have made all of the

...2/0x1aa Nov 23 13:54:09 dom0-u2 kernel: [ 3047.280855] [<ffffffff80471de7>] notifier_call_chain+0x57/0xb0 Nov 23 13:54:09 dom0-u2 kernel: [ 3047.280855] [<ffffffff80075a1c>] __raw_notifier_call_chain+0x1c/0x40 Nov 23 13:54:09 dom0-u2 kernel: [ 3047.280855] [<ffffffff8045b90f>] _cpu_down+0xaf/0x310 Nov 23 13:54:09 dom0-u2 kernel: [ 3047.280855] [<ffffffff8045bbf7>] cpu_down+0x87/0xb0 Nov 23 13:54:09 dom0-u2 kernel: [ 3047.280855] [<ffffffff8046a42c>] vcpu_hotplug+0xce/0x102 Nov 23 13:54:09 dom0-u2 kernel: [ 3047.280855] [<ffffffff8046a4ab>] handle_vcpu_hotplug_...

Dear all, i''m having problems passing a Hauppage Nova-S2 card to my DomU (Mythtv Backend). Hardware is: HP XW8200 2x 3.0GHz Xeon 8Gb ECC Ram 1x TT3200-S2 card 1x DVBWordl S2 card 1x Nova-S2 card [many other card for other domUs...] Dom0 is Ubuntu 8.04 server LTS. Xen 3.2 from repo. DomU (Mythtv) is a 8.04 (using LVM) both using 2.6.24-23-xen kernels Dom0 configs: lspci: ... 02:01.0

...u_hotplug_t) ) + goto parse_error; + + /* grab target vcpu from msg */ + handler->vcpu = req->vcpu; + + /* determine which function to call based on msg subtype */ + switch ( msg->subtype ) { + case CMSG_VCPU_HOTPLUG_OFF: + handler->fn = (void *)&cpu_down; + ret = schedule_work(&vcpu_hotplug_work); + req->status = (u32) ret; + break; + case CMSG_VCPU_HOTPLUG_ON: + handler->fn = (void *)&cpu_up; + ret = schedule_work(&vcpu_hotplug_work); + req->status = (u32) re...

This patch implements cpu offline feature. Best Regards Haitao Shan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -