On Wed, Mar 31, 2021 at 2:52 PM Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > On 30/03/21 07:48, Anup Patel wrote: > > > > It seems Andrew does not want to freeze H-extension until we have virtualization > > aware interrupt controller (such as RISC-V AIA specification) and IOMMU. Lot > > of us feel that these things can be done independently because RISC-V > > H-extension already has provisions for external interrupt controller with > > virtualization support. > > Yes, frankly that's pretty ridiculous as it's perfectly possible to > emulate the interrupt controller in software (and an IOMMU is not needed > at all if you are okay with emulated or paravirtualized devices---which > is almost always the case except for partitioning hypervisors). > > Palmer, are you okay with merging RISC-V KVM? Or should we place it in > drivers/staging/riscv/kvm? > > Either way, the best way to do it would be like this: > > 1) you apply patch 1 in a topic branch > > 2) you merge the topic branch in the risc-v tree > > 3) Anup merges the topic branch too and sends me a pull request. In any case, I will send v17 based on Linux-5.12-rc5 so that people can at least try KVM RISC-V based on latest kernel. Regards, Anup
