On Thu, 18 Feb 2021 at 06:10, Marc Zyngier <maz@xxxxxxxxxx> wrote: > > On Thu, 04 Feb 2021 07:51:37 +0000, > Haibo Xu <haibo.xu@xxxxxxxxxx> wrote: > > > > Kindly ping! > > > > On Thu, 21 Jan 2021 at 11:03, Haibo Xu <haibo.xu@xxxxxxxxxx> wrote: > > > > > > Re-send in case the previous email was blocked for the inlined hyper-link. > > > > > > Hi Marc, > > > > > > I have tried to enable the NV support in Qemu, and now I can > > > successfully boot a L2 guest > > > in Qemu KVM mode. > > > > > > This patch series looks good from the Qemu side except for two minor > > > requirements: > > > (1) Qemu will check whether a feature was supported by the KVM cap > > > when the user tries to enable it in the command line, so a new > > > capability was prefered for the NV(KVM_CAP_ARM_NV?). > > I have added KVM_CAP_ARM_EL2 (rather than NV) to that effect. > > > > (2) According to the Documentation/virt/kvm/api.rst, userspace can > > > call KVM_ARM_VCPU_INIT multiple times for a given vcpu, but the > > > kvm_vcpu_init_nested() do have some issue when called multiple > > > times(please refer to the detailed comments in patch 63) > > This is now fixed, I believe. > > I have pushed out a branch [1] that addresses all the reported > issues, though it currently lack some testing. Please let me know if > it works for you. > Hi Marc, I have verified the fix, and it works well with Qemu. thanks, Haibo > Thanks, > > M. > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=kvm-arm64/nv-5.12-WIP > > -- > Without deviation from the norm, progress is not possible. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
