From: Keir Fraser Subject: Re: [PATCH] Allow guest to register a secondary vcpu_time_info structure Date: Tue, 06 Oct 2009 08:10:27 +0100 Message-ID: References: <4ACA8AE6.3000602@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4ACA8AE6.3000602@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Dan Magenheimer , Xen-devel List-Id: xen-devel@lists.xenproject.org On 06/10/2009 01:10, "Jeremy Fitzhardinge" wrote: > The second vcpu_time_info structure is updated by copy, rather than > being a shared page between the guest and Xen. It is not directly > updated by copy; instead, Xen preserves and increments the existing > version number in place. This allows the guest to also update the > version number (useful to indicate vcpu context switches to usermode). > This assumes that the guest will only ever update the structure for a > given vcpu on that vcpu (as Xen does, so there are never any cross-cpu > accesses). How do you feel about the 32-bit version number? We have space to easily expand it to 64 bits, and now would be the time to do it while we're extending the ABI. -- Keir