Re: [Xen-devel] watches not working from domU userspace

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 7 Jan 2006, at 10:06, Cihula, Joseph wrote:

> The connection sud-id approach also has the option of keeping the same
> suspend behavior since that only depends on snooping the communication
> and not maintaining any state (other than the mutex).  And if drivers
> use the sub-ids, I think that more transaction and watch bookkeeping
> could be removed from xenbus.  And the grant table change to
> XS_INTRODUCE that I mentioned works either way.
>
> Are there additional benefits to the grants approach besides just
> removing xenbus from the communication path?
Yes, I think maybe you are right. I missed that the connection id can 
conveniently be used to demux watch events. That given, I think 
piggybacking connections is the way to go after all.
Reusing the request_id as a conn_id should work fine, since all current 
clients just set that field to zero. Do you intend to introduce new 
commands like XS_CREATE_CONNECTION / XS_DESTROY_CONNECTION? I think 
that those ought to be executable only by the root connection 
(connection 0).
 -- Keir


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