All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: hypercall_xlat_continuation()
Date: Thu, 28 May 2009 20:01:08 -0700	[thread overview]
Message-ID: <4A1F4FF4.1010904@oracle.com> (raw)
In-Reply-To: <4A1DF87A.5050008@oracle.com>



Mukesh Rathor wrote:
> 
> 
> Ian Campbell wrote:
>> On Sat, 2009-05-23 at 06:17 -0400, 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.
>>
>> It's worth noting though that I don't believe a 32 bit dom0 toolstack on
>> a 64 bit kernel on a 64 bit hypervisor will work. In particular the
>> privcmd "make a hypercall" ioctl doesn't do any compat translation so 32
>> bit xend and friends can't make hypercalls that way and I think the
>> MMAPBATCH privcmd doesn't work either.
>>
>> I'm sure there are other cases too (blktap user<->kernel ring layout
>> maybe?).
>>
>> Ian.
> 
> Thanks Ian for good explanation of hypercall_xlat_continuation().
> 
> yeah, I'm just exploring that right now. There is MMAPBATCH_32, btw, in
> dom0 that looks like was implemented by PPC folks. Also, MMAP_32.
> I was able to start PV guest without network. Not sure if that was
> because of compatibility or some other issue. I'm just looking at MMAP
> stuff right now, think I finally figured out the chain of calls from
> libxc to hyp to dom0 ... ia32_sys_call_table to compat_sys_ioctl to
> handler to do_ioctl32_pointer .. whew!!
> 
> Thanks,
> Mukesh
> 

yeah, looks like privcmd_ioctl_32() only fixes the wrapper struct. The
PFN array still is 32bit pfn's, and privcmd_ioctl() expects 64bits. So,
in a dilemma now, not sure if I should fix it up in privcmd_ioctl_32()
or change privcmd_ioctl() which will take some time to reverse engineer.
Not sure how many things I'll discover, if it's too many, it may
not be worth it in the end.

Thanks,
Mukesh

  reply	other threads:[~2009-05-29  3:01 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           ` Mukesh Rathor [this message]
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       ` hypercall_xlat_continuation() Mukesh Rathor
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=4A1F4FF4.1010904@oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Ian.Campbell@citrix.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.