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 6/7, RFC] x86_64: basic changes for supporting co

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 23 Aug 2006 12:17:02 +0200
Delivery-date: Wed, 23 Aug 2006 03:17:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C111E116.143E%Keir.Fraser@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: <44EC38F1.76E4.0078.0@xxxxxxxxxx> <C111E116.143E%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 23.08.06 11:40 >>>
>On 23/8/06 10:16 am, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
>
>> This changes the ABI in adding to vcpu_guest_context - does a change like
>> this require bumping the ABI version?
>
>We can't do this as the struct is part of the domU ABI (used for
>initialising secondary VCPUs). You'll have to add the extra CS values to
>64-bit arch_vcpu, I think.

Then libxc/xc_linux_build.c (after appropriate adjustment) wouldn't have
a way to communicate these for a new domain. If extending the structure
isn't possible at all, then we'll either have to make event_callback_eip and
failsafe_callback_eip unions (permitting a selector:offset pair) or make
syscall_callback_eip a union (permitting storing the selectors). I'd favor
the second option as that field is entirely useless as long as x86_32
doesn't support syscall (which doesn't make sense as it would make
things slower rather than speeding them up) - that way one doesn't have
to be careful to not access the other two full 64bit *_callback_eip
fields.

Jan

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