On 22.10.2009, at 12:23, Avi Kivity wrote:
On 10/21/2009 04:08 PM, Alexander Graf wrote:
From: Arnd Bergmanna...@arndb.de
With big endian userspace, we can't quite figure out if a pointer
is 32 bit (shifted 32) or 64 bit when we read a 64 bit pointer.
This is what happens with dirty
From: Arnd Bergmann a...@arndb.de
With big endian userspace, we can't quite figure out if a pointer
is 32 bit (shifted 32) or 64 bit when we read a 64 bit pointer.
This is what happens with dirty logging. To get the pointer interpreted
correctly, we thus need Arnd's patch to implement a compat
On Wednesday 21 October 2009, Alexander Graf wrote:
KVM for PowerPC only supports embedded cores at the moment.
While it makes sense to virtualize on small machines, it's even more fun
to do so on big boxes. So I figured we need KVM for PowerPC64 as well.
This patchset implements KVM
On Wed, Oct 21, 2009 at 04:08:29PM +0200, Alexander Graf wrote:
From: Arnd Bergmann a...@arndb.de
With big endian userspace, we can't quite figure out if a pointer
is 32 bit (shifted 32) or 64 bit when we read a 64 bit pointer.
This is what happens with dirty logging. To get the pointer
On Wed, 2009-10-21 at 17:03 +0200, Alexander Graf wrote:
KVM for PowerPC only supports embedded cores at the moment.
While it makes sense to virtualize on small machines, it's even more fun
to do so on big boxes. So I figured we need KVM for PowerPC64 as well.
This patchset implements KVM
The old BUILD_BUG_ON implementation didn't work with __builtin_constant_p().
Fixing that revealed this test had been inverted for a long time without
anybody noticing...
Signed-off-by: Hollis Blanchard holl...@us.ibm.com
diff --git a/arch/powerpc/kvm/timing.h b/arch/powerpc/kvm/timing.h
---
On Tue, Oct 20, 2009 at 10:43 PM, Alan Jenkins
sourcejedi.l...@googlemail.com wrote:
On 10/20/09, Américo Wang xiyou.wangc...@gmail.com wrote:
On Tue, Oct 20, 2009 at 02:15:33PM +1030, Rusty Russell wrote:
BUILD_BUG_ON used to use the optimizer to do code elimination or fail
at link time; it was
