Re: [win-pv-devel] Detecting event channel disconnect

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-
> bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Rafal Wojdyla
> Sent: 18 May 2015 15:14
> To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [win-pv-devel] Detecting event channel disconnect
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> Am I correct in the assumption that currently a Windows event channel
> peer can't easily detect if the other peer has closed the remote end?

Yes, that's correct. There's no interface exposed for that.

> I'm not 100% sure on how the low-level evtchn hypervisor API works in
> that case but it seems that there's no notification.
> 
> If the above is correct I think adding a EVTCHNOP_status call to
> xenbus API would allow for easy status querying.
> 

Yes, wiring that through the EVTCHN interface - with suitable abstraction - 
sounds ok. However, it does beg the question of why the guest needs to know?

  Paul

> - --
> RafaÅ WojdyÅa
> Qubes Tools for Windows developer
> -----BEGIN PGP SIGNATURE-----
> 
> iQEcBAEBAgAGBQJVWfOKAAoJEIWi9rB2GrW78ZQH/jQhiqYVjA4Zde4xLpP5jS
> uN
> fkgpVlg2XJg+3D2bQ0SzCY+PkfqVXmDvK33La2k8XxocbYmrlbhrUj29R65MUUq
> N
> oY4dX/bAWuIqlCxwR1l9hMngELzpuVs74jj5ztNembjahKdf8x2gBcoOwPJy2As
> H
> uaZf3Fi6eJMx7V/2f6MslubFkKhkkzB+ue9Te9f3kDCuMliXml4XCOjqkVRMT+7
> B
> t4q2qCjcji4jt8nYqlWleagdAq/KCJXHtZl1ZpJLMDRLb2R7vigSMc/VEaUcahiw
> C4WGA3UW7TpxH1AyqVtkeVDiE7JcjgI1EWUiNCh1gdWAiGlG6xpXTYvTK2e34
> G8=
> =0MQU
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> win-pv-devel mailing list
> win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel