search for: 1,844

On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala wrote: > This provides a generic interface for paravirtual drivers to listen > for netdev register/unregister/link change events from pci ethernet > devices with the same MAC and takeover their datapath. The notifier and > event handling cod...

On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala wrote: > This provides a generic interface for paravirtual drivers to listen > for netdev register/unregister/link change events from pci ethernet > devices with the same MAC and takeover their datapath. The notifier and > event handling cod...

Tue, Apr 10, 2018 at 08:59:48PM CEST, sridhar.samudrala at intel.com wrote: >This provides a generic interface for paravirtual drivers to listen >for netdev register/unregister/link change events from pci ethernet >devices with the same MAC and takeover their datapath. The notifier and >event hand...

Tue, Apr 10, 2018 at 08:59:48PM CEST, sridhar.samudrala at intel.com wrote: >This provides a generic interface for paravirtual drivers to listen >for netdev register/unregister/link change events from pci ethernet >devices with the same MAC and takeover their datapath. The notifier and >event hand...

...paravirtual drivers to listen for netdev register/unregister/link change events from pci ethernet devices with the same MAC and takeover their datapath. The notifier and event handling code is based on the existing netvsc implementation. It exposes 2 sets of interfaces to the paravirtual drivers. 1. existing netvsc driver that uses 2 netdev model. In this model, no master netdev is created. The paravirtual driver registers each bypass instance along with a set of ops to manage the slave events. bypass_master_register() bypass_master_unregister() 2. new virtio_net based solution that...

...paravirtual drivers to listen for netdev register/unregister/link change events from pci ethernet devices with the same MAC and takeover their datapath. The notifier and event handling code is based on the existing netvsc implementation. It exposes 2 sets of interfaces to the paravirtual drivers. 1. existing netvsc driver that uses 2 netdev model. In this model, no master netdev is created. The paravirtual driver registers each instance of netvsc as a 'failover' instance along with a set of ops to manage the slave events. failover_register() failover_unregister() 2. new vir...

On 4/19/2018 7:44 PM, Michael S. Tsirkin wrote: > On Thu, Apr 19, 2018 at 06:42:02PM -0700, Sridhar Samudrala wrote: >> This provides a generic interface for paravirtual drivers to listen >> for netdev register/unregister/link change events from pci ethernet >> devices with the same M...

On 4/11/2018 8:51 AM, Jiri Pirko wrote: > Tue, Apr 10, 2018 at 08:59:48PM CEST, sridhar.samudrala at intel.com wrote: >> This provides a generic interface for paravirtual drivers to listen >> for netdev register/unregister/link change events from pci ethernet >> devices with the same...

...tch is to enable cloud service providers to provide an accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes. This also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices. Patch 1 introduces a new feature bit VIRTIO_NET_F_BACKUP that can be used by hypervisor to indicate that virtio_net interface should act as a backup for another device with the same MAC address. Patch 2 introduces a bypass module that provides a generic interface for paravirtual drivers to listen for net...

...tch is to enable cloud service providers to provide an accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes. This also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices. Patch 1 introduces a new feature bit VIRTIO_NET_F_STANDBY that can be used by hypervisor to indicate that virtio_net interface should act as a standby for another device with the same MAC address. Patch 2 introduces a failover module that provides a generic interface for paravirtual drivers to listen for...

Wed, Apr 11, 2018 at 09:13:52PM CEST, sridhar.samudrala at intel.com wrote: >On 4/11/2018 8:51 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 08:59:48PM CEST, sridhar.samudrala at intel.com wrote: >> > This provides a generic interface for paravirtual drivers to listen >> > for netde...

Wed, Apr 11, 2018 at 09:13:52PM CEST, sridhar.samudrala at intel.com wrote: >On 4/11/2018 8:51 AM, Jiri Pirko wrote: >> Tue, Apr 10, 2018 at 08:59:48PM CEST, sridhar.samudrala at intel.com wrote: >> > This provides a generic interface for paravirtual drivers to listen >> > for netde...

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches

...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 hvc console (console=hvc0) * virtual block device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks needed by Xen 13-24: the Xen guest implementation itself (Some of the earlier patches in the series have already been posted, but are included to make the series self-contained.) I've tried to...

...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 hvc console (console=hvc0) * virtual block device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks needed by Xen 13-24: the Xen guest implementation itself (Some of the earlier patches in the series have already been posted, but are included to make the series self-contained.) I've tried to...

...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 hvc console (console=hvc0) * virtual block device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks needed by Xen 13-24: the Xen guest implementation itself (Some of the earlier patches in the series have already been posted, but are included to make the series self-contained.) I've tried to...

...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 device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks for Xen 13-21: the Xen guest implementation itself I've tried to make each patch as self-explanatory as possible. The series is based on 2.6.20 + Andi Kleen's firstfloor patches, specifical...

...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 device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks for Xen 13-21: the Xen guest implementation itself I've tried to make each patch as self-explanatory as possible. The series is based on 2.6.20 + Andi Kleen's firstfloor patches, specifical...

...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 device (blockfront) * virtual network device (netfront) The patch series is in two parts: 1-12: cleanups to the core kernel, either to fix outright problems, or to add appropriate hooks for Xen 13-21: the Xen guest implementation itself I've tried to make each patch as self-explanatory as possible. The series is based on 2.6.20 + Andi Kleen's firstfloor patches, specifical...

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