From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [RFC PATCH 12/45] KVM: arm/arm64: vgic-new: Add MMIO handling framework Date: Thu, 31 Mar 2016 14:25:02 +0200 Message-ID: <56FD171E.1040401@redhat.com> References: <1458871508-17279-1-git-send-email-andre.przywara@arm.com> <1458871508-17279-13-git-send-email-andre.przywara@arm.com> <20160331090824.GR4126@cbox> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Marc Zyngier , Eric Auger , "linux-arm-kernel@lists.infradead.org" , "kvmarm@lists.cs.columbia.edu" , "kvm@vger.kernel.org" To: Christoffer Dall , Andre Przywara Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53615 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751243AbcCaMZH (ORCPT ); Thu, 31 Mar 2016 08:25:07 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 31/03/2016 11:09, Christoffer Dall wrote: >> My comments to Vladimir's bug report notwithstanding, there's still a >> choice here to: >> >> 1) Expand/modify the KVM IO bus framework to take an arbitrary number of devices >> >> 2) Build a KVM architectureal generic framework on top of the IO bus >> framework to handle individual register regions. >> >> 3) Stick with what we had before, do not modify the KVM IO bus stuff, >> and handle the individual register region business locally within the >> arm/vgic code. I prefer 3, or alternatively just add the framework in virt/kvm/arm so that it can be migrated to virt/kvm if someone else needs it. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: pbonzini@redhat.com (Paolo Bonzini) Date: Thu, 31 Mar 2016 14:25:02 +0200 Subject: [RFC PATCH 12/45] KVM: arm/arm64: vgic-new: Add MMIO handling framework In-Reply-To: References: <1458871508-17279-1-git-send-email-andre.przywara@arm.com> <1458871508-17279-13-git-send-email-andre.przywara@arm.com> <20160331090824.GR4126@cbox> Message-ID: <56FD171E.1040401@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 31/03/2016 11:09, Christoffer Dall wrote: >> My comments to Vladimir's bug report notwithstanding, there's still a >> choice here to: >> >> 1) Expand/modify the KVM IO bus framework to take an arbitrary number of devices >> >> 2) Build a KVM architectureal generic framework on top of the IO bus >> framework to handle individual register regions. >> >> 3) Stick with what we had before, do not modify the KVM IO bus stuff, >> and handle the individual register region business locally within the >> arm/vgic code. I prefer 3, or alternatively just add the framework in virt/kvm/arm so that it can be migrated to virt/kvm if someone else needs it. Paolo