And add a new flag definition in kvm_ppc_pvinfo to indicate
whether host support EV_IDLE hcall.
Signed-off-by: Liu Yu yu@freescale.com
---
v2:
1. instead of adding new field in kvm_ppc_pvinfo, use flags.
2. expose hcall definitions to userspace
arch/powerpc/include/asm/kvm_para.h | 14
On 01/04/2012 08:36 PM, Alexander Graf wrote:
On 04.01.2012, at 21:12, Scott Wood wrote:
On 01/03/2012 07:10 PM, Alexander Graf wrote:
diff --git a/arch/powerpc/include/asm/kvm.h b/arch/powerpc/include/asm/kvm.h
index 25964ee..fb3fddc 100644
--- a/arch/powerpc/include/asm/kvm.h
+++
On 01/04/2012 10:07 PM, Alexander Graf wrote:
Ok here's another idea on how to handle this. What if we encode the
register size in the constant? That way, if the register grows later,
we can still be backwards compatible, but give user space exactly the
size it asks for.
We could then just
On 05.01.2012, at 18:16, Scott Wood wrote:
On 01/04/2012 08:36 PM, Alexander Graf wrote:
On 04.01.2012, at 21:12, Scott Wood wrote:
On 01/03/2012 07:10 PM, Alexander Graf wrote:
diff --git a/arch/powerpc/include/asm/kvm.h
b/arch/powerpc/include/asm/kvm.h
index 25964ee..fb3fddc 100644
This is a revised version of the ONE_REG interface. The main difference to v1
is that we now encode the register size in the constant, making it very
unambiguous what size it is. That way we can just take a pointer from user space
to write it to.
Thanks a lot to Scott for reviewing the previous
Right now we transfer a static struct every time we want to get or set
registers. Unfortunately, over time we realize that there are more of
these than we thought of before and the extensibility and flexibility of
transferring a full struct every time is limited.
So this is a new approach to the
Until now, we always set HIOR based on the PVR, but this is just wrong.
Instead, we should be setting HIOR explicitly, so user space can decide
what the initial HIOR value is - just like on real hardware.
We keep the old PVR based way around for backwards compatibility, but
once user space uses
On 06.01.2012, at 04:59, Alexander Graf wrote:
Right now we transfer a static struct every time we want to get or set
registers. Unfortunately, over time we realize that there are more of
these than we thought of before and the extensibility and flexibility of
transferring a full struct
Hey Alex,
On 24/12/11 00:39, Alexander Graf wrote:
On 23.12.2011, at 14:26, Matt Evans wrote:
On 23/12/2011, at 11:58 PM, Alexander Graf wrote:
On 13.12.2011, at 07:21, Matt Evans wrote:
Different architectures will deal with MMIO exits differently. For
example,
KVM_EXIT_IO is
