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,
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,
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.
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
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.
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