Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751996AbaGGHa7 (ORCPT ); Mon, 7 Jul 2014 03:30:59 -0400 Received: from fw-tnat.austin.arm.com ([217.140.110.23]:16778 "EHLO collaborate-mta1.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751163AbaGGHa6 convert rfc822-to-8bit (ORCPT ); Mon, 7 Jul 2014 03:30:58 -0400 From: Marc Zyngier To: Alex =?utf-8?Q?Benn=C3=A9e?= Cc: "kvmarm\@lists.cs.columbia.edu" , "linux-arm-kernel\@lists.infradead.org" , "kvm\@vger.kernel.org" , Christoffer Dall , Gleb Natapov , Paolo Bonzini , Russell King , Catalin Marinas , Will Deacon , open list Subject: Re: [PATCH] arm64: KVM: allow export and import of generic timer regs In-Reply-To: <1404485654-32674-1-git-send-email-alex.bennee@linaro.org> ("Alex \=\?utf-8\?Q\?Benn\=C3\=A9e\=22's\?\= message of "Fri, 4 Jul 2014 15:54:14 +0100") Organization: ARM Ltd References: <1404485654-32674-1-git-send-email-alex.bennee@linaro.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Date: Mon, 07 Jul 2014 08:30:41 +0100 Message-ID: <87mwclbp7i.fsf@why.wild-wind.fr.eu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 04 2014 at 3:54:14 pm BST, Alex Bennée wrote: > For correct guest suspend/resume behaviour we need to ensure we include > the generic timer registers for 64 bit guests. As CONFIG_KVM_ARM_TIMER is > always set for arm64 we don't need to worry about null implementations. > However I have re-jigged the kvm_arm_timer_set/get_reg declarations to > be in the common include/kvm/arm_arch_timer.h headers. > > Signed-off-by: Alex Bennée Acked-by: Marc Zyngier M. -- Without deviation from the norm, progress is not possible. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/