From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: hypercall_xlat_continuation() Date: Tue, 26 May 2009 11:43:48 -0700 Message-ID: <4A1C3864.30002@oracle.com> References: Reply-To: mukesh.rathor@oracle.com 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: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Jan Beulich List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 22/05/2009 22:58, "Mukesh Rathor" wrote: > >> Ok. Even if I can't make it clearer, at least I'll add few lines of comments >> explaining what's going on, after (and if) I figure it out. >> >> Jan, >> >> It seems assumption is made that a 64bit dom0 will not have a 32bit app making >> hypercall? >> >> BUG_ON(*reg != (unsigned int)*reg); <==== > > You know that all the 'xlat' stuff in Xen is for 32-bit guests running on > 64-bit hypervisor, right? 64-bit dom0 would never execute this logic. Unless someone like me, in trying to make 32bit apps on 64bit dom0 work, causes it to take compat path if it's 32bit hcall. Yeah, I know whacky :)... Thanks as always, Mukesh PS: If anyone is curious, if the call is 32bit hcall, in entry.S I make it jmp to compat/entry.S and do compat hcall. So far, other than this xlat stuff, seems ok! I set a register in dom0 to before hcall to indicate it's from a 32bit app.