From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catalin Marinas Subject: Re: [PATCH v3 09/11] ARM: KVM: introduce per-vcpu HYP Configuration Register Date: Thu, 6 Feb 2014 11:01:48 +0000 Message-ID: <20140206110147.GF29446@arm.com> References: <1391630151-7875-1-git-send-email-marc.zyngier@arm.com> <1391630151-7875-10-git-send-email-marc.zyngier@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-arm-kernel@lists.infradead.org" , "kvmarm@lists.cs.columbia.edu" , "kvm@vger.kernel.org" , Christoffer Dall To: Marc Zyngier Return-path: Received: from fw-tnat.austin.arm.com ([217.140.110.23]:56450 "EHLO collaborate-mta1.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754010AbaBFLC0 (ORCPT ); Thu, 6 Feb 2014 06:02:26 -0500 Content-Disposition: inline In-Reply-To: <1391630151-7875-10-git-send-email-marc.zyngier@arm.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Feb 05, 2014 at 07:55:49PM +0000, Marc Zyngier wrote: > So far, KVM/ARM used a fixed HCR configuration per guest, except for > the VI/VF/VA bits to control the interrupt in absence of VGIC. > > With the upcoming need to dynamically reconfigure trapping, it becomes > necessary to allow the HCR to be changed on a per-vcpu basis. > > The fix here is to mimic what KVM/arm64 already does: a per vcpu HCR > field, initialized at setup time. > > Signed-off-by: Marc Zyngier > Reviewed-by: Christoffer Dall Acked-by: Catalin Marinas