From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Re: [Xen-changelog] Indirect hypercalls through a hypercall transfer page. Date: Wed, 08 Feb 2006 09:37:12 -0600 Message-ID: <43EA1028.203@us.ibm.com> References: <1139374660.11984.30.camel@localhost.localdomain> <79c457384536c20ab5b2bb2ce6238895@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <79c457384536c20ab5b2bb2ce6238895@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Gerrit Huizenga , xen-devel , Hollis Blanchard List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > Allows a different hypercall implementation on platforms where that > makes sense. For example, we would like to run XenLinux on native by > running it over a small 'Xen shim' that provides the Xen API but no > protection or multiplexing. In that case it would be most efficient to > turn syscall instructions into jumps. Is someone working on this? I had been thinking of something like this myself. A pretty straight-forward kernel module that could allow you to run XenLinux on native (so we could have our own "player"). Regards, Anthony Liguori > -- Keir > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >