From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: HVM hypercalls Date: Thu, 29 Jul 2010 12:47:00 -0700 Message-ID: <4C51DAB4.4030007@goop.org> References: <559459.12230.qm@web113620.mail.gq1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <559459.12230.qm@web113620.mail.gq1.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ruslan Nikolaev Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 07/29/2010 11:55 AM, Ruslan Nikolaev wrote: > Thank you very much! I'll try this. BTW is it required to do this for every module with HVM hypercalls or there is some shared initialization code in HVM guest (Linux) similar to one used in paravirtualized guests? > > If it's supposed to be in a module, is there any good example I can look at? > > AFAIK hypercall_page is being initialized on Xen side with appropriate vmcall/vmmcall code. Is this CPUID mechanism a standard way to obtain hypercall_page reference on HVM domain? What kernel are you working with? There's already code to implement pv-on-hvm support for various recent pvops kernels, so you can just base your work on those. J