search for: irqfd

...ns(-) > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index 00c88c2..20c07d3 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -10624,11 +10624,17 @@ int kvm_arch_irq_bypass_add_producer(struct irq_bypass_consumer *cons, > { > struct kvm_kernel_irqfd *irqfd = > container_of(cons, struct kvm_kernel_irqfd, consumer); > + int ret; > > irqfd->producer = prod; > + kvm_arch_start_assignment(irqfd->kvm); > + ret = kvm_x86_ops.update_pi_irte(irqfd->kvm, > + prod->irq, irqfd->gsi, 1); > + > + if (ret...

...ns(-) > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index 00c88c2..20c07d3 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -10624,11 +10624,17 @@ int kvm_arch_irq_bypass_add_producer(struct irq_bypass_consumer *cons, > { > struct kvm_kernel_irqfd *irqfd = > container_of(cons, struct kvm_kernel_irqfd, consumer); > + int ret; > > irqfd->producer = prod; > + kvm_arch_start_assignment(irqfd->kvm); > + ret = kvm_x86_ops.update_pi_irte(irqfd->kvm, > + prod->irq, irqfd->gsi, 1); > + > + if (ret...

...ns(-) > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index 00c88c2..20c07d3 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -10624,11 +10624,17 @@ int kvm_arch_irq_bypass_add_producer(struct irq_bypass_consumer *cons, > { > struct kvm_kernel_irqfd *irqfd = > container_of(cons, struct kvm_kernel_irqfd, consumer); > + int ret; > > irqfd->producer = prod; > + kvm_arch_start_assignment(irqfd->kvm); > + ret = kvm_x86_ops.update_pi_irte(irqfd->kvm, > + prod->irq, irqfd->gsi, 1); > + > + if (ret...

Hi Shannon, >Type of backend bandwith(GBytes/sec) >virtio-net 0.66 >vhost-net 1.49 >vhost-net with irqfd 2.01 > >Test cmd: ./iperf -c 192.168.0.2 -P 1 -i 10 -p 5001 -f G -t 60 Impressive results ! Could you please detail your setup ? which platform are you using and which GbE controller ? As a reference, it would be good also to have result with an iperf to the HOST to see how far we are fro...

Hi Shannon, >Type of backend bandwith(GBytes/sec) >virtio-net 0.66 >vhost-net 1.49 >vhost-net with irqfd 2.01 > >Test cmd: ./iperf -c 192.168.0.2 -P 1 -i 10 -p 5001 -f G -t 60 Impressive results ! Could you please detail your setup ? which platform are you using and which GbE controller ? As a reference, it would be good also to have result with an iperf to the HOST to see how far we are fro...

...ns(-) > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index 00c88c2..20c07d3 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -10624,11 +10624,17 @@ int kvm_arch_irq_bypass_add_producer(struct irq_bypass_consumer *cons, > { > struct kvm_kernel_irqfd *irqfd = > container_of(cons, struct kvm_kernel_irqfd, consumer); > + int ret; > > irqfd->producer = prod; > + kvm_arch_start_assignment(irqfd->kvm); > + ret = kvm_x86_ops.update_pi_irte(irqfd->kvm, > + prod->irq, irqfd->gsi, 1); > + > + if (ret...

...O_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, and different handler will be assigned. >> >> If you want to add a new register you should probably propose >> an update to the virtio spec. However, it seems to me it would >> be better to get generic PCI...

...O_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, and different handler will be assigned. >> >> If you want to add a new register you should probably propose >> an update to the virtio spec. However, it seems to me it would >> be better to get generic PCI...

...ich >>>> 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, and different handler will be assigned. >>> >>> If you want to add a new register you should probably propose >>> an update to the virtio spec. However, it seems to me it would >>> be bette...

...ich >>>> 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, and different handler will be assigned. >>> >>> If you want to add a new register you should probably propose >>> an update to the virtio spec. However, it seems to me it would >>> be bette...

On 2014/10/26 19:52, Michael S. Tsirkin wrote: > On Sat, Oct 25, 2014 at 04:24:52PM +0800, john.liuli wrote: >> From: Li Liu <john.liuli at huawei.com> >> >> This set of patches try to implemet irqfd support of vhost-net >> based on virtio-mmio. >> >> I had posted a mail to talking about the status of vhost-net >> on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html. >> Some dependent patches are listed in the mail too. Basically the >> v...

On 2014/10/26 19:52, Michael S. Tsirkin wrote: > On Sat, Oct 25, 2014 at 04:24:52PM +0800, john.liuli wrote: >> From: Li Liu <john.liuli at huawei.com> >> >> This set of patches try to implemet irqfd support of vhost-net >> based on virtio-mmio. >> >> I had posted a mail to talking about the status of vhost-net >> on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html. >> Some dependent patches are listed in the mail too. Basically the >> v...

On Sat, Oct 25, 2014 at 04:24:52PM +0800, john.liuli wrote: > From: Li Liu <john.liuli at huawei.com> > > This set of patches try to implemet irqfd support of vhost-net > based on virtio-mmio. > > I had posted a mail to talking about the status of vhost-net > on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html. > Some dependent patches are listed in the mail too. Basically the > vhost-net brings great p...

...>> 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, and different handler will be assigned. >>>> >>>> If you want to add a new register you should probably propose >>>> an update to the virtio spec. However, it seems to me it would >&...

Hi R?my, On 2014/11/5 16:26, GAUGUEY R?my 228890 wrote: > Hi Shannon, > >> Type of backend bandwith(GBytes/sec) >> virtio-net 0.66 >> vhost-net 1.49 >> vhost-net with irqfd 2.01 >> >> Test cmd: ./iperf -c 192.168.0.2 -P 1 -i 10 -p 5001 -f G -t 60 > > Impressive results ! > Could you please detail your setup ? which platform are you using and which GbE controller ? Sorry for not telling the test scenario. This test scenario is from Host to Gue...

...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, and different handler will be assigned. If you want to add a new register you should probably propose an update to the virtio spec. However, it seems to me it would be better to get generic PCI/PCIe working on the ARM virt board instead...

...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, and different handler will be assigned. If you want to add a new register you should probably propose an update to the virtio spec. However, it seems to me it would be better to get generic PCI/PCIe working on the ARM virt board instead...

..., 2014 at 05:19:23PM +0800, Li Liu wrote: > > > On 2014/10/26 19:52, Michael S. Tsirkin wrote: > > On Sat, Oct 25, 2014 at 04:24:52PM +0800, john.liuli wrote: > >> From: Li Liu <john.liuli at huawei.com> > >> > >> This set of patches try to implemet irqfd support of vhost-net > >> based on virtio-mmio. > >> > >> I had posted a mail to talking about the status of vhost-net > >> on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html. > >> Some dependent patches are listed in the mail too....

From: Li Liu <john.liuli at huawei.com> This set of patches try to implemet irqfd support of vhost-net based on virtio-mmio. I had posted a mail to talking about the status of vhost-net on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html. Some dependent patches are listed in the mail too. Basically the vhost-net brings great performance improvements, almos...

From: Li Liu <john.liuli at huawei.com> This set of patches try to implemet irqfd support of vhost-net based on virtio-mmio. I had posted a mail to talking about the status of vhost-net on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html. Some dependent patches are listed in the mail too. Basically the vhost-net brings great performance improvements, almos...