| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] Signalling DomU on TPR write |
| From: | "James Harper" <james.harper@xxxxxxxxxxxxxxxx> |
| Date: | Thu, 1 Jan 2009 11:57:37 +1100 |
| Delivery-date: | 2008年12月31日 16:58:06 -0800 |
| 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 |
| Thread-index: | Aclrq/CHzsnJS6rURJmB2SpgYv3Pew== |
| Thread-topic: | Signalling DomU on TPR write |
Keir (and anyone else with an opinion on this :), Given that you have suggested that patching from the hypervisor might have synchronisation issues, my current thought on a mechanism for signalling a DomU when a TPR write occurs is this: . DomU allocates a page and makes a hypercall to the hypervisor saying "put info about TPR writes here" and use this event channel to signal me. . When a TPR write occurs, the hypervisor fills in the entry in the buffer nominated above and sets a flag. Until the flag is cleared, the hypervisor does no further signalling. . The guest sees the event (via the interrupt - same as any other event), patches the kernel as appropriate, then clears the flag . Repeat until all the places are patched. Obviously a number of iterations will be required before all the patching is done, but I don't think that's a problem. Patching would occur in the DomU with all processors at HIGH_LEVEL (interrupts disabled). Does that sound acceptable? Thanks James _______________________________________________ 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: 2.6.26-rc8 pv_ops causes Unhandled invalid opcode fault/trap , Jeremy Fitzhardinge |
|---|---|
| Previous by Thread: | [Xen-devel] extending create_bounce_frame , Swapna Shingre |
| Indexes: | [Date] [Thread] [Top] [All Lists] |