[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [win-pv-devel] New Dev and issues



  How did you attempt to subscribe? It looks like the buttons on the main xenproject page donât take you to the mailman URL. Try going straight to http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel


  To answer your questions thoughâ


1)      I think the WMI interface should probably not stray much beyond xenstore access. Most other things (unless you have particular reason to want to implement them in .NET) will probably want an IOCTL interface. RafaÅ WojdyÅa <omeg@xxxxxxxxxxxxxxxxxxxxxx> has been doing work on adding libvchan support and has been using an IOCTL based interface to get at things like event channels. I believe he has patches in the pipeline.

2)      I believe it is currently safe to use both IOCTL and WMI xenstore access concurrently. If it isnât the Iâd regard that as a bug.







From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Mark Mueller
Sent: 23 June 2015 14:35
To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [win-pv-devel] New Dev and issues



I am working on a project for AIS to incorporate the Win PV Driver Project into OpenXT. I've submitted two requests to subscribe to this list but have not yet received a response.


I could use some help relative to the IOCTL and WMI interfaces exposed by Xeniface. I see examples of the WMI interface usage in the win32stubagent, but non for the IOCTL interface. These are my questions:


1) Is the WMI interface preferred over the IOCTL and is future dev expected to continue in that direction? For example when I add new OpenXT drivers, is dominant usage of the WMI interface encouraged?


2) Can both IOCTL and WMI xenstore interfaces be used concurrently without issue?


Thanks for any help,



win-pv-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.