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

[Mark Mueller <markkmueller@xxxxxxxxx>]

Hi Rafal,

Your work is very interesting, especially the IOCTL interfaces that you have added. If you don't mind a few questions, is this something that you are doing as a side project, or is it a primary focus? Do you expect to be doing the driver patches soon? I will probably start working from your branch, but it would be helpful to know more about its upstream prospects.

Thanks,

Mark

On Tue, Jun 23, 2015 at 5:00 PM, RafaÅ WojdyÅa <omeg@xxxxxxxxxxxxxxxxxxxxxx> wrote:

That's correct. I have a fully working libvchan implementation now. It
still needs some more testing and smoothing rough edges but once I have
finished porting our Qubes Tools I'll work on the driver patches.

I've added IOCTL interfaces for every functionality I needed:
- xenstore access including watches and setting permissions
- event channels
- grant tables (granting memory to other domains)
- mapping memory from other domains

These IOCTLs are accessed through a user-mode DLL (xencontrol) that
provides easier to use APIs similar to libxc.

The code is on my github: https://github.com/omeg
xenbus and xeniface are the two modified pvdriver repos.
qubes-vmm-xen-windows-pvdrivers contains the libxenvchan library. It's
rather ugly for now since it's pretty much a direct port from the linux
version. Hope that helps.

RafaÅ WojdyÅa
Qubes Tools for Windows developer
https://www.qubes-os.org/


On 2015-06-23 15:53, Paul Durrant wrote:
> Mark,
>
>Â Â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.
>
>Â ÂHTH,
>Â Â ÂPaul
>
>
> *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

>
> Hello,
>
> 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,
>
> Mark
>

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel