This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] code question xen/arch/x86/vmx.c

To: Jerone Young <jyoung5@xxxxxxxxxx>
Subject: Re: [Xen-devel] code question xen/arch/x86/vmx.c
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 11 Aug 2005 22:47:48 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 11 Aug 2005 21:51:57 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1123796900.3043.71.camel@thinkpad>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1123796900.3043.71.camel@thinkpad>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 11 Aug 2005, at 22:48, Jerone Young wrote:

In function vmx_dr_access in xen/arch/x86/vmx.c there is a long pointer
named "reg_p". reg_p is assigned to

v->arch.guest_context.debugreg[reg] = *reg_p;

in the switch case  TYPE_MOV_TO_DR.

yet it has no assignment before this? What is the intent of reg_p?

It also is assigned in the switch case TYPE_MOVE_FROM_DR...yet it's not
used for anything ?

It's assigned to in the macro CASE_GET_REG_P.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>