WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] rename VMX option lapic to apic, and pass it to

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] rename VMX option lapic to apic, and pass it to xen by hvm_info_table
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 3 Jan 2006 11:41:17 +0000
Cc: "Li, Xin B" <xin.b.li@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 03 Jan 2006 11:40:51 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <0781c15ff61fad902a03f7d06f8257c3@xxxxxxxxxxxx>
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: <59D45D057E9702469E5775CBB56411F10141D983@pdsmsx406> <0781c15ff61fad902a03f7d06f8257c3@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 2 Jan 2006, at 10:16, Keir Fraser wrote:

I like the name 'lapic' rather than 'apic' as it explicitly disambiguates from 'ioapic'. And it's only one more character.

Placing the hvm info definitions in public/io/ioreq.h is not right. It probably needs its own header file. How about a new subdirectory include/public/hvm, containing hvm_info.h, ioreq.h and vmx_assist.h?

Also, does anything in Xen actually use the nr_vcpus variable? There's an accessor function for obtaining its value, but noone calls it, nor can I see any reason someone would want to in the future. There's already a setmaxvcpus dom0_op. Seems the Xen code that reads that part of the hvm_info struct could be removed.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel