Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932862AbWCVWaz (ORCPT ); Wed, 22 Mar 2006 17:30:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932866AbWCVWaz (ORCPT ); Wed, 22 Mar 2006 17:30:55 -0500 Received: from cantor.suse.de ([195.135.220.2]:39653 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932862AbWCVWay (ORCPT ); Wed, 22 Mar 2006 17:30:54 -0500 From: Andi Kleen To: virtualization@lists.osdl.org Subject: Re: [RFC, PATCH 1/24] i386 Vmi documentation II Date: Wed, 22 Mar 2006 22:39:44 +0100 User-Agent: KMail/1.9.1 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 References: <200603131759.k2DHxeep005627@zach-dev.vmware.com> <200603222105.58912.ak@suse.de> In-Reply-To: <200603222105.58912.ak@suse.de> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200603222239.46604.ak@suse.de> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 527 Lines: 13 > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/