Xen devel - Jan 2008 - HYPERVISOR_memory_op XENMAPSPACE_shared_info failing under windows 64 bit

I''m now seeing what is involved in getting the windows GPL PV drivers
working under windows 64 bit (amd64), and it is crashing out almost
immediately.

I have confirmed with the debugger that I am mapping the hypercall stuff
in correctly, but when I try to map the shared info page in I get a -22
(-EINVAL).

Looking at the hypervisor code, the only place I can see where that code
path would return -EINVAL is:

"
        if ( !paging_mode_translate(d) || (mfn == 0) )
        {
            rcu_unlock_domain(d);
            return -EINVAL;
        }
"

So either mfn == 0, or (!paging_mode_translate(d)) == TRUE. The only way
I can see that the first could be true is if my xen_add_to_physmap
structure were corrupt or something.

Can anyone offer any suggestions?

Incidently, why is the gpfn field in xen_add_to_physmap only 32 bits?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 22/1/08 13:15, "James Harper" <james.harper@bendigoit.com.au>
wrote:
> Incidently, why is the gpfn field in xen_add_to_physmap only 32 bits?
That gives you 44 bits of addressing, or 16TB. Should be plenty.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel