[Xen-changelog] Also send xenbus notifications using evtchn as handle. It's

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 9d047fb99e388fa48d50b22e58884a133051d260
# Parent  78e1e94e4088b63bb5d66f070f036e7fc7f4df6e
Also send xenbus notifications using evtchn as handle. It's
always up-to-date as it's reinitialised for us by external
tools during save/restore and migration.

diff -r 78e1e94e4088 -r 9d047fb99e38 
linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c
--- a/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c    Fri Sep 30 
16:34:01 2005
+++ b/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c    Fri Sep 30 
16:37:52 2005
@@ -147,7 +147,7 @@
                data += avail;
                len -= avail;
                update_output_chunk(out, avail);
-               notify_remote_via_irq(xenbus_irq);
+               notify_remote_via_evtchn(xen_start_info->store_evtchn);
        } while (len != 0);
 
        return 0;
@@ -192,7 +192,7 @@
                pr_debug("Finished read of %i bytes (%i to go)\n", avail, len);
                /* If it was full, tell them we've taken some. */
                if (was_full)
-                       notify_remote_via_irq(xenbus_irq);
+                       notify_remote_via_evtchn(xen_start_info->store_evtchn);
        }
 
        /* If we left something, wake watch thread to deal with it. */

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