All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: hypercall_xlat_continuation()
Date: Tue, 26 May 2009 11:43:48 -0700	[thread overview]
Message-ID: <4A1C3864.30002@oracle.com> (raw)
In-Reply-To: <C63D8BDE.BAC5%keir.fraser@eu.citrix.com>



Keir Fraser wrote:
> On 22/05/2009 22:58, "Mukesh Rathor" <mukesh.rathor@oracle.com> 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.

  parent reply	other threads:[~2009-05-26 18:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22  2:57 hypercall_xlat_continuation() Mukesh Rathor
2009-05-22 16:29 ` hypercall_xlat_continuation() Keir Fraser
2009-05-22 21:58   ` hypercall_xlat_continuation() Mukesh Rathor
2009-05-23 10:17     ` hypercall_xlat_continuation() Keir Fraser
2009-05-23 22:44       ` hypercall_xlat_continuation() Ian Campbell
2009-05-28  2:35         ` hypercall_xlat_continuation() Mukesh Rathor
2009-05-29  3:01           ` hypercall_xlat_continuation() Mukesh Rathor
2009-05-29  9:54             ` hypercall_xlat_continuation() Ian Campbell
2009-06-02  0:03               ` hypercall_xlat_continuation() Mukesh Rathor
2009-05-26 18:43       ` Mukesh Rathor [this message]
2009-05-27  8:02         ` hypercall_xlat_continuation() Jan Beulich
2009-05-27  8:04           ` hypercall_xlat_continuation() Keir Fraser
2009-05-27  8:22             ` hypercall_xlat_continuation() Jan Beulich
2009-05-27  8:58               ` hypercall_xlat_continuation() Keir Fraser
2009-05-23 22:36 ` hypercall_xlat_continuation() Ian Campbell
2009-05-25 11:47   ` hypercall_xlat_continuation() Jan Beulich
2009-05-25 13:07     ` hypercall_xlat_continuation() Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A1C3864.30002@oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.