From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: portability issues
Date: Thu, 21 Jun 2007 10:58:04 +0100
Message-ID: <C2A00A3C.11047%keir@xensource.com>
References: <467A66B3.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <467A66B3.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org




On 21/6/07 10:53, "Jan Beulich" <jbeulich@novell.com> wrote:

>> (1) and (2): I want to kill off use of vcpu_guest_context in dom0 tools,
>> make hvm save/restore a generic state load/save interface, and define
>> extensible structures at that interface (pass a stream of state chunks back
>> and forth at the interface, each chunk having a size in its header, and so
>> increasing the size of a chunk allows it to be naturally appended to and
>> hence extended).
> 
> I wasn't concerned about the tools interface. The real compatibility problem
> is VCPUOP_initialize.

I don't see the problem. The guest will not be able to initialise secondary
VCPU's sysenter/syscall state via this interface. So what?

 -- Keir