search for: shutdown_halt

...86/kernel/crash.c 2006-03-08 11:34:53.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/kernel/crash.c 2006-03-08 11:38:09.000000000 -0800 @@ -113,7 +113,7 @@ static int crash_nmi_callback(struct pt_ disable_local_APIC(); atomic_dec(&waiting_for_crash_ipi); /* Assume hlt works */ - halt(); + shutdown_halt(); for(;;); return 1; Index: linux-2.6.16-rc5/arch/i386/kernel/process.c =================================================================== --- linux-2.6.16-rc5.orig/arch/i386/kernel/process.c 2006-03-08 11:38:06.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/kernel/process.c 2006-03-08 11:3...

...86/kernel/crash.c 2006-03-08 11:34:53.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/kernel/crash.c 2006-03-08 11:38:09.000000000 -0800 @@ -113,7 +113,7 @@ static int crash_nmi_callback(struct pt_ disable_local_APIC(); atomic_dec(&waiting_for_crash_ipi); /* Assume hlt works */ - halt(); + shutdown_halt(); for(;;); return 1; Index: linux-2.6.16-rc5/arch/i386/kernel/process.c =================================================================== --- linux-2.6.16-rc5.orig/arch/i386/kernel/process.c 2006-03-08 11:38:06.000000000 -0800 +++ linux-2.6.16-rc5/arch/i386/kernel/process.c 2006-03-08 11:3...

...and most importantly, halt and interrupt control, which is non-virtualizable. Since read_cr4_safe can never fault on a VMI kernel (P5+ processor is required for VMI), we can omit the fault fixup, which does not play well with the VMI inline assembler, and just call read_cr4() directly. Note that shutdown_halt is unused, but provided in case there is really a use for it. See arch/i386/kernel/smp.c for a potential call site during AP shutdown. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.16-rc5/include/asm-i386/system.h =========================================================...

...and most importantly, halt and interrupt control, which is non-virtualizable. Since read_cr4_safe can never fault on a VMI kernel (P5+ processor is required for VMI), we can omit the fault fixup, which does not play well with the VMI inline assembler, and just call read_cr4() directly. Note that shutdown_halt is unused, but provided in case there is really a use for it. See arch/i386/kernel/smp.c for a potential call site during AP shutdown. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.16-rc5/include/asm-i386/system.h =========================================================...

...ux/stringify.h> #include <asm/irq.h> #include <asm/mmu_context.h> +#include <asm/emergency-restart.h> #include <xen/evtchn.h> #include <asm/hypervisor.h> #include <xen/interface/dom0_ops.h> @@ -39,16 +40,11 @@ extern void ctrl_alt_del(void); */ #define SHUTDOWN_HALT 4 -void machine_emergency_restart(void) +void machine_restart(char * __unused) { /* We really want to get pending console data out before we die. */ xencons_force_flush(); HYPERVISOR_shutdown(SHUTDOWN_reboot); -} - -void machine_restart(char * __unused) -{ - machine_emergency_restart(...

...nage.c | 51 ++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 42 insertions(+), 9 deletions(-) diff --git a/drivers/xen/manage.c b/drivers/xen/manage.c index 3f8496c..323703a 100644 --- a/drivers/xen/manage.c +++ b/drivers/xen/manage.c @@ -36,8 +36,16 @@ enum shutdown_state { SHUTDOWN_HALT = 4, }; -/* Ignore multiple shutdown requests. */ -static enum shutdown_state shutting_down = SHUTDOWN_INVALID; +/* Ignore multiple shutdown requests. There are two potential race conditions: + * - Multiple XenStore ''shutdown'' requests. We don''t want to run any off +...

...ux/stringify.h> #include <asm/irq.h> #include <asm/mmu_context.h> +#include <asm/emergency-restart.h> #include <xen/evtchn.h> #include <asm/hypervisor.h> #include <xen/interface/dom0_ops.h> @@ -39,16 +40,11 @@ extern void ctrl_alt_del(void); */ #define SHUTDOWN_HALT 4 -void machine_emergency_restart(void) +void machine_restart(char * __unused) { /* We really want to get pending console data out before we die. */ xencons_force_flush(); HYPERVISOR_shutdown(SHUTDOWN_reboot); -} - -void machine_restart(char * __unused) -{ - machine_emergency_restart(...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git13 + patches-2.6.21-git7-070507-1.tar.gz (I think "unwinder" is the only patch which doesn't apply to git13, and the sched-clock patches are the only ones which this series actually needs). Changes since the last posting: - More netfront review and cleanup - Added ability to

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git13 + patches-2.6.21-git7-070507-1.tar.gz (I think "unwinder" is the only patch which doesn't apply to git13, and the sched-clock patches are the only ones which this series actually needs). Changes since the last posting: - More netfront review and cleanup - Added ability to

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git13 + patches-2.6.21-git7-070507-1.tar.gz (I think "unwinder" is the only patch which doesn't apply to git13, and the sched-clock patches are the only ones which this series actually needs). Changes since the last posting: - More netfront review and cleanup - Added ability to

Hi, This is the Xen implementation for the paravirt_ops interface. The series is based on 2.6.22-rc1-mm1, and I think its ready to be cooked in -mm with a view to being merged in 2.6.23. The first part of the series is some small changes to the core kernel. Apart from the new code added in "Allocate and free vmalloc areas" (posted many times before), they are simply a few one-liners

Hi, This is the Xen implementation for the paravirt_ops interface. The series is based on 2.6.22-rc1-mm1, and I think its ready to be cooked in -mm with a view to being merged in 2.6.23. The first part of the series is some small changes to the core kernel. Apart from the new code added in "Allocate and free vmalloc areas" (posted many times before), they are simply a few one-liners

Hi, This is the Xen implementation for the paravirt_ops interface. The series is based on 2.6.22-rc1-mm1, and I think its ready to be cooked in -mm with a view to being merged in 2.6.23. The first part of the series is some small changes to the core kernel. Apart from the new code added in "Allocate and free vmalloc areas" (posted many times before), they are simply a few one-liners