From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mike D. Day" Subject: Re: Re: [Xen-changelog] Indirect hypercalls through ahypercall transfer page. Date: Wed, 08 Feb 2006 10:46:19 -0500 Message-ID: <43EA124B.6020502@us.ibm.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com, Hollis Blanchard List-Id: xen-devel@lists.xenproject.org Ian Pratt wrote: >> What is this patch about? I mean I can see how it works, but >> what is the motivation for it? > > The primary reason for this patch is that it will enable us to run a > xenified kernel on bare metal: a 'micro xen' would be loaded by the boot > loader alongside a xenified kernel image, enabling the kernel to > effectively run on the baremetal at full native performance (though > obviously you could only run one kernel on a machine at a time). This is an elegant feature that would have been better introduced with the above explanation rather than a patchbot message. If I missed that discussion, apologies. Mike Day