search for: virtio_mmio_isrmem

From: Li Liu <john.liuli at huawei.com> Add a new register offset VIRTIO_MMIO_ISRMEM which help to estblish a shared memory region between virtio-mmio driver and qemu with two purposes: 1.Guest virtio-mmio driver can get the interrupt reason. 2.Check irqfd enabled or not to register different irq handler. Signed-off-by: Li Liu <john.liuli at huawei.com> --- drivers/virtio/...

...anage virtqueue operations". Vhost module don't update the ISR register, so if with only one irq then it's no way to get the interrupt reason even we can inject the irq correctly. 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 same time, the virtio-mmio dirver check this region to see irqfd is supported or not during the irq handler registration...

...anage virtqueue operations". Vhost module don't update the ISR register, so if with only one irq then it's no way to get the interrupt reason even we can inject the irq correctly. 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 same time, the virtio-mmio dirver check this region to see irqfd is supported or not during the irq handler registration...

On Sat, Oct 25, 2014 at 04:24:53PM +0800, john.liuli wrote: > From: Li Liu <john.liuli at huawei.com> > > Add a new register offset VIRTIO_MMIO_ISRMEM which help to > estblish a shared memory region between virtio-mmio driver > and qemu with two purposes: > > 1.Guest virtio-mmio driver can get the interrupt reason. > 2.Check irqfd enabled or not to register different irq handler. > > Signed-off-by: Li Liu <john.liuli at...

...014 12:23 PM, Li Liu wrote: > > > On 2014/10/27 17:37, Peter Maydell wrote: >> 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 same time, the virtio-mmio >>> dirver check this region to see irqfd is supp...

...014 12:23 PM, Li Liu wrote: > > > On 2014/10/27 17:37, Peter Maydell wrote: >> 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 same time, the virtio-mmio >>> dirver check this region to see irqfd is supp...

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 same time, the virtio-mmio > dirver check this region to see irqfd is supported or not during > the irq...

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 same time, the virtio-mmio > dirver check this region to see irqfd is supported or not during > the irq...

...pt reason instead of ISR regiser by qemu without bothering vhost. Then even there's only one irq with only one irq hanlder, it still can distinguish why irq occur. Li. > >> 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 same time, the virtio-mmio >> dirver check this region to see irqfd is supported or not...

...pt reason instead of ISR regiser by qemu without bothering vhost. Then even there's only one irq with only one irq hanlder, it still can distinguish why irq occur. Li. > >> 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 same time, the virtio-mmio >> dirver check this region to see irqfd is supported or not...

...then it's > no way to get the interrupt reason even we can inject the > irq correctly. Well guests don't read ISR in MSI-X mode so why does it help to set the ISR bit? > 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 same time, the virtio-mmio > dirver check this region to see irqfd is supported or not during > the...

On 2014/10/27 17:37, Peter Maydell wrote: > 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 same time, the virtio-mmio >> dirver check this region to see irqfd is supported or not dur...

...rote: >> >> >> On 2014/10/27 17:37, Peter Maydell wrote: >>> 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 same time, the virtio-mmio >>>> dirver check this region to s...

...rote: >> >> >> On 2014/10/27 17:37, Peter Maydell wrote: >>> 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 same time, the virtio-mmio >>>> dirver check this region to s...

...hich might be a handy optimization even for PCI (at the moment reading ISR causes an exit). Need to see how all this would work on MP systems though. > > > > >> 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 same time, the virtio-mmio > >> dirver check this region to see irqfd...

...gt;> >>> On 2014/10/27 17:37, Peter Maydell wrote: >>>> 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 same time, the virtio-mmio >>>>> dirver check...