On Mon, Mar 26, 2007 at 02:12:09PM -0500, Jerone Young wrote:
> While trying to verify any potential problem between with libvirt & Xen
> PPC port. I've found that libvirt currently in CVS attempts to determine
> what hypercall version to follow, by looking at the hypervisior version.
> It determin
While trying to verify any potential problem between with libvirt & Xen
PPC port. I've found that libvirt currently in CVS attempts to determine
what hypercall version to follow, by looking at the hypervisior version.
It determines that this is some arbitrary versioning "v2" of the
hypercall api. T
Hi, all the PowerPC changes are now merged into
http://xenbits.xensource.com/xen-unstable.hg . Please test this tree and
report any problems, because these bits are the ones that will go into
the 3.0.5 release which will go into Linux distributions.
http://xenbits.xensource.com/ext/linux-ppc-2.6.h
On Mar 26, 2007, at 8:26 AM, Christian Ehrhardt wrote:
Jimi Xenidis wrote:
On Mar 23, 2007, at 9:07 AM, Hollis Blanchard wrote:
Right, that won't fit in EXCEPTION_HEAD (you will get the assembler
error messages Jimi pasted above).
Yeah,
So EXCEPTION_HEAD branches to a passed in label. Fin
Jimi Xenidis wrote:
On Mar 23, 2007, at 9:07 AM, Hollis Blanchard wrote:
On Fri, 2007-03-23 at 08:52 +0100, Christian Ehrhardt wrote:
Jimi Xenidis wrote:
...
Ensure MMCR0[FCH] for this first step:
-(ensure) set MMCR[FCH] always in xen when entering xen space. This
should prevent a domain
me
