search for: emuluation

...;> thanks >> -- PMM >> > > So you mean virtio-mmio will be replaced by PCI/PCIe on ARM at last? > If so, let this patch go with the wind:). Thx. Hi, As a fix of current situation where ISR is only partially updated when vhost-irqfd handles standard IRQ and waiting for PCI emuluation, wouldn't it make sense to store ISR content on vhost driver side and introduce ioctls to read/write it. When using vhost BE, virtio QEMU device would use those ioctl to read/update the ISR content. On top of that we would update the ISR in vhost before triggering the irqfd. If I do not miss an...

...;> thanks >> -- PMM >> > > So you mean virtio-mmio will be replaced by PCI/PCIe on ARM at last? > If so, let this patch go with the wind:). Thx. Hi, As a fix of current situation where ISR is only partially updated when vhost-irqfd handles standard IRQ and waiting for PCI emuluation, wouldn't it make sense to store ISR content on vhost driver side and introduce ioctls to read/write it. When using vhost BE, virtio QEMU device would use those ioctl to read/update the ISR content. On top of that we would update the ISR in vhost before triggering the irqfd. If I do not miss an...

...; >> >> So you mean virtio-mmio will be replaced by PCI/PCIe on ARM at last? >> If so, let this patch go with the wind:). Thx. > > Hi, > > As a fix of current situation where ISR is only partially updated when > vhost-irqfd handles standard IRQ and waiting for PCI emuluation, > wouldn't it make sense to store ISR content on vhost driver side and > introduce ioctls to read/write it. When using vhost BE, virtio QEMU > device would use those ioctl to read/update the ISR content. On top of > that we would update the ISR in vhost before triggering the irqfd....

...; >> >> So you mean virtio-mmio will be replaced by PCI/PCIe on ARM at last? >> If so, let this patch go with the wind:). Thx. > > Hi, > > As a fix of current situation where ISR is only partially updated when > vhost-irqfd handles standard IRQ and waiting for PCI emuluation, > wouldn't it make sense to store ISR content on vhost driver side and > introduce ioctls to read/write it. When using vhost BE, virtio QEMU > device would use those ioctl to read/update the ISR content. On top of > that we would update the ISR in vhost before triggering the irqfd....

...you mean virtio-mmio will be replaced by PCI/PCIe on ARM at last? >>> If so, let this patch go with the wind:). Thx. >> >> Hi, >> >> As a fix of current situation where ISR is only partially updated when >> vhost-irqfd handles standard IRQ and waiting for PCI emuluation, >> wouldn't it make sense to store ISR content on vhost driver side and >> introduce ioctls to read/write it. When using vhost BE, virtio QEMU >> device would use those ioctl to read/update the ISR content. On top of >> that we would update the ISR in vhost before trigg...

On 25 October 2014 09:24, john.liuli <john.liuli at huawei.com> wrote: > To get the interrupt reason to support such VIRTIO_NET_F_STATUS > features I add a new register offset VIRTIO_MMIO_ISRMEM which > will help to establish a shared memory region between qemu and > virtio-mmio device. Then the interrupt reason can be accessed by > guest driver through this region. At the

On 25 October 2014 09:24, john.liuli <john.liuli at huawei.com> wrote: > To get the interrupt reason to support such VIRTIO_NET_F_STATUS > features I add a new register offset VIRTIO_MMIO_ISRMEM which > will help to establish a shared memory region between qemu and > virtio-mmio device. Then the interrupt reason can be accessed by > guest driver through this region. At the