 Home |
Products |
Support |
Community |
News |
xen-ppc-devel
[XenPPC] paravirt_ops
| To: | "xen-ppc-devel" <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [XenPPC] paravirt_ops |
| From: | "Yoder Stuart-B08248" <stuart.yoder@xxxxxxxxxxxxx> |
| Date: | Mon, 15 Jan 2007 11:21:54 -0700 |
| Delivery-date: | Mon, 15 Jan 2007 10:21:30 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen PPC development <xen-ppc-devel.lists.xensource.com> |
| List-post: | <mailto:xen-ppc-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| Thread-index: | Acc40gi+M+G/5DQgQAq52yKTva+Ylw== |
| Thread-topic: | paravirt_ops |
Is paravirt_ops an X86 thing only? I'm assuming this ops structure in Linux was to enable VMware and Xen to share a common OS-to-hypervisor interface. On Linux/powerpc we don't need this because we don't have competing hypervisors. Correct? Thanks, Stuart _______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ppc-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [XenPPC] IPI problems, Jimi Xenidis |
|---|---|
| Next by Date: | Re: [XenPPC] paravirt_ops, Hollis Blanchard |
| Previous by Thread: | [XenPPC] IPI problems, Hollis Blanchard |
| Next by Thread: | Re: [XenPPC] paravirt_ops, Hollis Blanchard |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
