| To: | "Jeremy Fitzhardinge" <jeremy@xxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] xenbus_dev_request_and_reply() checking for transaction end |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | 2007年10月18日 12:30:03 +0100 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | 2007年10月18日 04:34:26 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Jeremy, what is the motivation for doing if ((msg->type == XS_TRANSACTION_END) || where linux-2.6.18-xen does if ((req_msg.type == XS_TRANSACTION_END) || ? Is the intention to continue holding the mutex if sending the transaction end message fails? If so, wouldn't this also require all users of xenbus_transaction_end() to do proper error checking *and* re-issuing? Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] VMX status report against cset #16125 & linux-xen#263 -- two fixed issues , You, Yongkang |
|---|---|
| Next by Date: | [Xen-devel] unregister_xenbus_watch() handling of xenwatch_mutex , Jan Beulich |
| Previous by Thread: | [Xen-devel] VMX status report against cset #16125 & linux-xen#263 -- two fixed issues , You, Yongkang |
| Next by Thread: | [Xen-devel] unregister_xenbus_watch() handling of xenwatch_mutex , Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |