search for: machine_restart

...cihula@intel.com> diff -r a53aaea4c698 -r a85c4081738a xen/arch/ia64/xen/domain.c --- a/xen/arch/ia64/xen/domain.c Fri Sep 07 19:54:29 2007 +0100 +++ b/xen/arch/ia64/xen/domain.c Fri Sep 07 17:37:01 2007 -0700 @@ -1486,7 +1486,7 @@ int __init construct_dom0(struct domain return 0; } -void machine_restart(char * __unused) +void machine_restart(int __unused) { console_start_sync(); if (running_on_sim) diff -r a53aaea4c698 -r a85c4081738a xen/arch/powerpc/domain.c --- a/xen/arch/powerpc/domain.c Fri Sep 07 19:54:29 2007 +0100 +++ b/xen/arch/powerpc/domain.c Fri Sep 07 17:37:01 2007 -0700 @@ -119,...

# HG changeset patch # User Hollis Blanchard <hollisb@us.ibm.com> # Date 1154990956 18000 # Node ID 058f2e27476d686538de2671f57c1ded5c693b47 # Parent 4196687234c530a11d26a199f1479bc07e08248f [XEN] Remove redundant redeclaration of ''machine_restart''. Fixes compile warning with gcc 3.4.2. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> diff -r 4196687234c5 -r 058f2e27476d xen/drivers/char/console.c --- a/xen/drivers/char/console.c Mon Aug 07 17:36:58 2006 -0500 +++ b/xen/drivers/char/console.c Mon Aug 07 17:49:16 2006 -050...

...u_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(); } void machine_halt(void) ___________________________________...

...u_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(); } void machine_halt(void) ___________________________________...

...ommu_for_device amd_iommu_ioapic_update_ire timer_interrupt enable_8259_A_irq do_IRQ printk_start_of_line acpi_os_printf io_apic_write __ioapic_write_entry ioapic_write_entry __clear_IO_APIC_pin clear_IO_APIC disable_IO_APIC __stop_this_cpu smp_send_stop machine_restart panic tasklet_schedule_on_cpu display_cacheinfo init_amd generic_identify identify_cpu _start_xen _high_start This patch fixes this by keeping the iommu disabled until iommu_setup() is entered. Signed-off-by: Ronny Hegewald@online.de --- xen/drivers/passthrough/iommu.c...

...m screen, so it might contain typos) find_iommu_for_device amd_iommu_ioapic_update_ire timer_interrupt enable_8259_A_irq do_IRQ printk_start_of_line acpi_os_printf io_apic_write __ioapic_write_entry ioapic_write_entry __clear_IO_APIC_pin clear_IO_APIC disable_IO_APIC __stop_this_cpu smp_send_stop machine_restart panic tasklet_schedule_on_cpu display_cacheinfo init_amd generic_identify identify_cpu _start_xen _high_start Panic on CPU 0: Xen BUG at pci_amd_iommu.c:33 ===== The patch in the next mail fixes the problem for me and the intended panic- message appears.

...the cache, @@ -322,6 +318,9 @@ void machine_shutdown(void) void machine_emergency_restart(void) { +#ifdef CONFIG_X86_VMI + vmi_reboot(!reboot_thru_bios); +#endif if (!reboot_thru_bios) { if (efi_enabled) { efi.reset_system(EFI_RESET_COLD, EFI_SUCCESS, 0, NULL); @@ -352,6 +351,7 @@ void machine_restart(char * __unused) void machine_halt(void) { + shutdown_halt(); } void machine_power_off(void) Index: linux-2.6.16-rc5/arch/i386/kernel/smp.c =================================================================== --- linux-2.6.16-rc5.orig/arch/i386/kernel/smp.c 2006-03-08 11:34:53.000000000 -080...

...the cache, @@ -322,6 +318,9 @@ void machine_shutdown(void) void machine_emergency_restart(void) { +#ifdef CONFIG_X86_VMI + vmi_reboot(!reboot_thru_bios); +#endif if (!reboot_thru_bios) { if (efi_enabled) { efi.reset_system(EFI_RESET_COLD, EFI_SUCCESS, 0, NULL); @@ -352,6 +351,7 @@ void machine_restart(char * __unused) void machine_halt(void) { + shutdown_halt(); } void machine_power_off(void) Index: linux-2.6.16-rc5/arch/i386/kernel/smp.c =================================================================== --- linux-2.6.16-rc5.orig/arch/i386/kernel/smp.c 2006-03-08 11:34:53.000000000 -080...

Hi all, I'm running OCFS2 on two system with OpenSUSE 10.2 connected on fibre channel with a shared storage (HP MSA1500 + HP PROLIANT MSA20). The cluster has two node (web-ha1 and web-ha2), sometimes (1 or 2 times on a month) the OCFS2 stop to work on both system. On the first node I'm getting no error in log files and after a forced shoutdown of the first node on the second I can see

...fiber cable to the RAID (in order to force a migration to a failover node) I expect to see I/O errors and then a failure to write/read to the filesystem, but in addition I get an Assertion failure. The end result is of course an unusable system which needs to be rebooted. (I reboot the system via machine_restart which works okay but I guess a regular reboot will get stuck) My kernel is basically 2.4.18-14 with a couple of patches applied mainly in networking area - nothing within miles of the ext3/filesystems area. Is this a known issue ? Dec 24 13:48:34 10.17.0.2 kernel: I/O error: dev 08:33, sector...

...+0x1e2/0x2e0 [ 17.157004] [<c01055d2>] die+0xf2/0x220 [ 17.157004] [<c03306d4>] do_general_protection+0x164/0x210 [ 17.157004] [<c03300c2>] error_code+0x6a/0x70 [ 17.157004] [<c0110449>] machine_emergency_restart+0x9/0x10 [ 17.157004] [<c011045d>] native_machine_restart+0xd/0x10 [ 17.157004] [<c0110469>] machine_restart+0x9/0x10 [ 17.157004] [<c0126be3>] kernel_restart+0x43/0x50 [ 17.157004] [<c0126d2f>] sys_reboot+0x12f/0x190 [ 17.157004] [<c010417e>] syscall_call+0x7/0xb [ 17.157004] ======================= [ 17.157004] C...

...+0x1e2/0x2e0 [ 17.157004] [<c01055d2>] die+0xf2/0x220 [ 17.157004] [<c03306d4>] do_general_protection+0x164/0x210 [ 17.157004] [<c03300c2>] error_code+0x6a/0x70 [ 17.157004] [<c0110449>] machine_emergency_restart+0x9/0x10 [ 17.157004] [<c011045d>] native_machine_restart+0xd/0x10 [ 17.157004] [<c0110469>] machine_restart+0x9/0x10 [ 17.157004] [<c0126be3>] kernel_restart+0x43/0x50 [ 17.157004] [<c0126d2f>] sys_reboot+0x12f/0x190 [ 17.157004] [<c010417e>] syscall_call+0x7/0xb [ 17.157004] ======================= [ 17.157004] C...

This patch series implements SMP boot for arch/arm, as far as getting all CPUs up and running the idle loop. Changes from v1: - moved barriers out of loop in udelay() - dropped broken GIC change in favour of explanatory comment - made the increment of ready_cpus atomic (I couldn''t move the increment to before signalling the next CPU because the PT switch has to happen between

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

Hello everyone, this is the fourth 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

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

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