| To: | "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] new hypercall implementation question |
| From: | Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> |
| Date: | 2009年7月23日 07:31:13 -0700 (PDT) |
| Delivery-date: | 2009年7月23日 07:31:46 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Is it safe to pass three guest virtual addresses via a hypercall to Xen and expect Xen to safely copy data (two scalars and one array of pagesize-bytes... not necessarily aligned on a page boundary) back to the guest, or do I need to do something fancy to avoid weird corner cases, e.g. to ensure restartabililty in case of guest page fault? This is a privileged-only hypercall used only as part of save/restore/live-migrate (for tmem) if that is relevant. Thanks, Dan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Re: [Xen-users] Xen viridian support/features , Tim Deegan |
|---|---|
| Next by Date: | Re: [Xen-devel] Re: [Xen-users] Xen viridian support/features , Florian Manschwetus |
| Previous by Thread: | [Xen-devel] [PATCH] tools: python portability fixes , Christoph Egger |
| Next by Thread: | Re: [Xen-devel] new hypercall implementation question , Jeremy Fitzhardinge |
| Indexes: | [Date] [Thread] [Top] [All Lists] |