 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] swiotlb
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] swiotlb |
| From: | "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx> |
| Date: | Thu, 13 Apr 2006 14:29:24 -0600 |
| Delivery-date: | Thu, 13 Apr 2006 13:30:08 -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 |
Given that the function __sync_single() can be called in an interrupt context, why do we call a potentially blocking function (__copy_to_user) from within this function? Regards, K. Y _______________________________________________ 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] Re: [PATCH][FIX] Possible fix for spurious interrupts, Stephen C. Tweedie |
|---|---|
| Next by Date: | [Xen-devel] Xen 3.0.2 released!, Ian Pratt |
| Previous by Thread: | [Xen-devel] [PATCH][FIX] Possible fix for spurious interrupts, Keir Fraser |
| Next by Thread: | Re: [Xen-devel] swiotlb, Don Dutile |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
