From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v2 0/9] arm64: KVM: debug infrastructure support Date: Sun, 25 May 2014 16:34:21 +0100 Message-ID: <20140525153421.GA3866@lvm> References: <1400604945-25247-1-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, Will Deacon , Catalin Marinas , Ian Campbell , Anup Patel , Peter Maydell To: Marc Zyngier Return-path: Received: from mail-la0-f49.google.com ([209.85.215.49]:55621 "EHLO mail-la0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751362AbaEYPe0 (ORCPT ); Sun, 25 May 2014 11:34:26 -0400 Received: by mail-la0-f49.google.com with SMTP id pv20so5256090lab.36 for ; Sun, 25 May 2014 08:34:24 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1400604945-25247-1-git-send-email-marc.zyngier@arm.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, May 20, 2014 at 05:55:36PM +0100, Marc Zyngier wrote: > This patch series adds debug support, a key feature missing from the > KVM/arm64 port. > > The main idea is to keep track of whether the debug registers are > "dirty" (changed by the guest) or not. In this case, perform the usual > save/restore dance, for one run only. It means we only have a penalty > if a guest is actively using the debug registers. > > The amount of registers is properly frightening, but CPUs actually > only implement a subset of them. Also, there is a number of registers > we don't bother emulating (things having to do with external debug and > OSlock). What is the rationale about not having to deal with external debug and OSlock? -Christoffer