[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[XenPPC] paravirt_ops

To: "xen-ppc-devel" <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
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
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
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

Follow-Ups:
- Re: [XenPPC] paravirt_ops
  - From: Hollis Blanchard

Prev by Date: Re: [XenPPC] IPI problems
Next by Date: Re: [XenPPC] paravirt_ops
Previous by thread: [XenPPC] IPI problems
Next by thread: Re: [XenPPC] paravirt_ops
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.