From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation Date: Fri, 09 Oct 2015 09:06:42 +0100 Message-ID: <56177592.2080702@arm.com> References: <1444247430-14808-1-git-send-email-christoffer.dall@linaro.org> <00e601d10264$61cdafb0$25690f10$@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, 'Andre Przywara' , 'Peter Maydell' , 'Eric Auger' To: Pavel Fedin , 'Christoffer Dall' , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Return-path: Received: from foss.arm.com ([217.140.101.70]:37673 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756015AbbJIIGp (ORCPT ); Fri, 9 Oct 2015 04:06:45 -0400 In-Reply-To: <00e601d10264$61cdafb0$25690f10$@samsung.com> Sender: kvm-owner@vger.kernel.org List-ID: On 09/10/15 08:30, Pavel Fedin wrote: > Hello! > >> + KVM_DEV_ARM_VGIC_CPU_SYSREGS >> + Attributes: >> + The attr field of kvm_device_attr encodes two values: >> + bits: | 63 .... 32 | 31 .... 16 | 15 .... 0 | >> + values: | mpidr | RES | instr | > > One small clarification: do you really want it to be different from KVM_DEV_ARM_VGIC_GRP_CPU_REGS? One is memory mapped, the other one is a system register. One is addressed by a linear index, the other one by affinity. How do you reconcile the two? What's the point of trying to shoehorn a different concept into the existing API? M. -- Jazz is not dead. It just smells funny...