Hi Anup, On 01/10/14 11:34, Anup Patel wrote: > This patchset updates KVMTOOL to use some of the features > supported by Linux-3.16 KVM ARM/ARM64, such as: > > 1. Target CPU == Host using KVM_ARM_PREFERRED_TARGET vm ioctl > 2. Target CPU type Potenza for using KVMTOOL on X-Gene > 3. PSCI v0.2 support for Aarch32 and Aarch64 guest > 4. System event exit reason Thanks for the quick respin. Looks fine now for me. For the whole v5 series: Reviewed-by: Andre Przywara <andre.przywara@xxxxxxx> Cheers, Andre. > Changes since v4: > - Avoid using magic '0' target for kvm arm generic target > - Added comment for why we need Potenza target in KVMTOOL > > Changes since v3: > - Add generic targets for aarch32 and aarch64 which are used > by KVMTOOL when target type returned by KVM_ARM_PREFERRED_TARGET > vm ioctl is not known to KVMTOOL > - Print more info when handling system reset event > > Changes since v2: > - Use target type returned by KVM_ARM_PREFERRED_TARGET vm ioctl > for VCPU init such that we don't need to update KVMTOOL for > every new host hardware > - Simplify DTB generation for PSCI node > > Changes since v1: > - Drop the patch to fix compile error for aarch64 > - Fallback to old method of trying all target types if > KVM_ARM_PREFERRED_TARGET vm ioctl fails > - Print more info when handling KVM_EXIT_SYSTEM_EVENT > > Anup Patel (4): > kvmtool: ARM: Use KVM_ARM_PREFERRED_TARGET vm ioctl to determine > target cpu > kvmtool: ARM64: Add target type potenza for aarch64 > kvmtool: Handle exit reason KVM_EXIT_SYSTEM_EVENT > kvmtool: ARM/ARM64: Provide PSCI-0.2 to guest when KVM supports it > > tools/kvm/arm/aarch32/arm-cpu.c | 8 +++ > tools/kvm/arm/aarch64/arm-cpu.c | 23 ++++++++- > tools/kvm/arm/fdt.c | 51 +++++++++++++++++-- > tools/kvm/arm/include/arm-common/kvm-cpu-arch.h | 2 + > tools/kvm/arm/kvm-cpu.c | 61 +++++++++++++++++++---- > tools/kvm/kvm-cpu.c | 21 ++++++++ > 6 files changed, 149 insertions(+), 17 deletions(-) > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
