From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v2] KVM: arm/arm64: avoid using kvm_run for in-kernel emulation Date: Mon, 13 Apr 2015 11:57:34 +0200 Message-ID: <20150413095734.GH6186@cbox> References: <1428677987-15494-1-git-send-email-andre.przywara@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: marc.zyngier@arm.com, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org To: Andre Przywara Return-path: Content-Disposition: inline In-Reply-To: <1428677987-15494-1-git-send-email-andre.przywara@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org On Fri, Apr 10, 2015 at 03:59:47PM +0100, Andre Przywara wrote: > Our in-kernel VGIC emulation still uses struct kvm_run briefly before > writing back the emulation result into the guest register. > Although this particular case looks safe from an exploitation > perspective, we can save some unneeded copying at the end of the VGIC > emulation code. > Replace the usage of struct kvm_run in favour of passing separate > parameters in io_mem_abort(). Since the write back is now handled > for all kvm_io_bus users, we can get rid of it in the VGIC. > > Signed-off-by: Andre Przywara Reviewed-by: Christoffer Dall