Xen project Mailing List

Yes. XenstoreWrite is basically superfluous since itâs just a specific case of XenstorePrintf.

Paul

From: Mark Mueller [mailto:markkmueller@xxxxxxxxx]
Sent: 23 June 2015 19:11
To: Paul Durrant
Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [win-pv-devel] New Dev and issues

I'll try using XenstorePrintf instead of XenstoreWrite

On Tue, Jun 23, 2015 at 12:04 PM, Mark Mueller <markkmueller@xxxxxxxxx> wrote:

On Tue, Jun 23, 2015 at 7:53 AM, Paul Durrant <Paul.Durrant@xxxxxxxxxx> 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

I did use this page to subscribe, it reports that I successfully submitted my subscription request.

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.

Great, thanks! By the way, does anyone have any idea of where body of the XenstoreWrite function slipped off to? I don't see it anywhere in the win32stubagent code. I am working from the master branch of xeniface. I guess I'll use WMI for the read and IOCTL for the write.

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

Yes, thanks,

Mark

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