Re: [PATCH v3 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend

2015-01-29 Thread Christoffer Dall
On Tue, Jan 27, 2015 at 05:44:26PM +, Andre Przywara wrote: Hi, On 27/01/15 17:26, Eric Auger wrote: On 01/27/2015 05:51 PM, Nikolay Nikolaev wrote: Hi Andre, On Tue, Jan 27, 2015 at 3:31 PM, Andre Przywara andre.przyw...@arm.com wrote: Hi Nikolay, On 24/01/15 11:59,

Re: [PATCH v3 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend

2015-01-29 Thread Nikolay Nikolaev
On Tue, Jan 27, 2015 at 7:44 PM, Andre Przywara andre.przyw...@arm.com wrote: Hi, On 27/01/15 17:26, Eric Auger wrote: On 01/27/2015 05:51 PM, Nikolay Nikolaev wrote: Hi Andre, On Tue, Jan 27, 2015 at 3:31 PM, Andre Przywara andre.przyw...@arm.com wrote: Hi Nikolay, On 24/01/15 11:59,

Re: [PATCH v3 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend

2015-01-27 Thread Nikolay Nikolaev
Hi Andre, On Tue, Jan 27, 2015 at 3:31 PM, Andre Przywara andre.przyw...@arm.com wrote: Hi Nikolay, On 24/01/15 11:59, Nikolay Nikolaev wrote: In io_mem_abort remove the call to vgic_handle_mmio. The target is to have a single MMIO handling path - that is through the kvm_io_bus_ API.

Re: [PATCH v3 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend

2015-01-27 Thread Andre Przywara
Hi Nikolay, On 24/01/15 11:59, Nikolay Nikolaev wrote: In io_mem_abort remove the call to vgic_handle_mmio. The target is to have a single MMIO handling path - that is through the kvm_io_bus_ API. Register a kvm_io_device in kvm_vgic_init on the whole vGIC MMIO region. Both read and write

Re: [PATCH v3 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend

2015-01-27 Thread Andre Przywara
Hi, On 27/01/15 17:26, Eric Auger wrote: On 01/27/2015 05:51 PM, Nikolay Nikolaev wrote: Hi Andre, On Tue, Jan 27, 2015 at 3:31 PM, Andre Przywara andre.przyw...@arm.com wrote: Hi Nikolay, On 24/01/15 11:59, Nikolay Nikolaev wrote: In io_mem_abort remove the call to vgic_handle_mmio.

[PATCH v3 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend

2015-01-24 Thread Nikolay Nikolaev
In io_mem_abort remove the call to vgic_handle_mmio. The target is to have a single MMIO handling path - that is through the kvm_io_bus_ API. Register a kvm_io_device in kvm_vgic_init on the whole vGIC MMIO region. Both read and write calls are redirected to vgic_io_dev_access where kvm_exit_mmio