From: Andi Kleen Subject: Re: [RFC, PATCH 1/24] i386 Vmi documentation II Date: Wed, 22 Mar 2006 22:39:44 +0100 Message-ID: <200603222239.46604.ak@suse.de> References: <200603131759.k2DHxeep005627@zach-dev.vmware.com> <200603222105.58912.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200603222105.58912.ak@suse.de> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: virtualization@lists.osdl.org Cc: Zachary Amsden , Linus Torvalds , Linux Kernel Mailing List , Xen-devel , Andrew Morton , Dan Hecht , Dan Arai , Anne Holler , Pratap Subrahmanyam , Christopher Li , Joshua LeVasseur , Chris Wright , Rik Van Riel , Jyothy Reddy , Jack Lo , Kip Macy , Jan Beulich , Ky Srinivasan , Wim Coekaerts , Leendert van Doorn List-Id: xen-devel@lists.xenproject.org > There was one other point I wanted to make but I forgot it now @) Ah yes the point was that since most of the implementations of the hypercalls likely need fast access to some per CPU state. How would you plan to implement that? Should it be covered in the specification? -Andi