search for: tty_insert_flip_char

...re initialised and used via the virtio_console driver, I can interact with only the first console, the 2nd one doesn't respond. If I call hvc_kick() even if hvc_poll() returns 0, the 2nd console becomes responsive. I've checked that hvc_poll() receives data via get_chars() and feeds it to tty_insert_flip_char(). Any idea what could be going wrong? This is reproducible on Linus' git kernel as the guest kernel with the qemu.git repo. Any pointers? Thanks, Amit

...re initialised and used via the virtio_console driver, I can interact with only the first console, the 2nd one doesn't respond. If I call hvc_kick() even if hvc_poll() returns 0, the 2nd console becomes responsive. I've checked that hvc_poll() receives data via get_chars() and feeds it to tty_insert_flip_char(). Any idea what could be going wrong? This is reproducible on Linus' git kernel as the guest kernel with the qemu.git repo. Any pointers? Thanks, Amit

...d xencons_rx(char *buf, unsigned len) > { > int i; > unsigned long flags; >@@ -328,21 +304,18 @@ > spin_lock_irqsave(&xencons_lock, flags); > if ( xencons_tty != NULL ) > { >- for ( i = 0; i < msg->length; i++ ) >- tty_insert_flip_char(xencons_tty, msg->msg[i], 0); >+ for ( i = 0; i < len; i++ ) >+ tty_insert_flip_char(xencons_tty, buf[i], 0); > tty_flip_buffer_push(xencons_tty); > } > spin_unlock_irqrestore(&xencons_lock, flags); > >- msg->length = 0; >-...

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

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