search for: xencons_force_flush

...ypervisor.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) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...-2007-08-07/include/xen/xencons.h 2007-08-09 12:10:06.000000000 +0200 @@ -2,7 +2,7 @@ #define __ASM_XENCONS_H__ struct dom0_vga_console_info; -void dom0_init_screen_info(const struct dom0_vga_console_info *info); +void dom0_init_screen_info(const struct dom0_vga_console_info *, size_t); void xencons_force_flush(void); void xencons_resume(void); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ypervisor.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) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187. (Should be identical to this patch from last

...xencons_tx_flush_task_routine, >- NULL); >- > #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0) > static struct tty_driver *xencons_driver; > #else >@@ -264,39 +257,22 @@ > /*** Forcibly flush console data before dying. ***/ > void xencons_force_flush(void) > { >- ctrl_msg_t msg; > int sz; > > /* Emergency console is synchronous, so there''s nothing to flush. */ > if ( xen_start_info.flags & SIF_INITDOMAIN ) > return; > >- /* >- * We use dangerous control-interface...

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

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual