WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] HYPERVISOR_memory_op XENMAPSPACE_shared_info failing under w

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] HYPERVISOR_memory_op XENMAPSPACE_shared_info failing under windows 64 bit
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Wed, 23 Jan 2008 00:15:38 +1100
Delivery-date: Tue, 22 Jan 2008 05:16:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Achc+OG6dDrZ/MR9T6et0LU+WYG5zg==
Thread-topic: 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>