On Fri, Oct 19, 2012 at 2:19 AM, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote: > Rusty Russell <rusty@xxxxxxxxxxxxxxx> writes: >> Avi Kivity <avi@xxxxxxxxxx> writes: >>> On 09/05/2012 10:58 AM, Rusty Russell wrote: >>>> This is the generic part of the KVM_SET_ONE_REG/KVM_GET_ONE_REG >>>> enhancements which ARM wants, rebased onto kvm/next. >>> >>> This was stalled for so long it needs rebasing again, sorry. >>> >>> But otherwise I'm happy to apply. >> >> Ok, will rebase and re-test against kvm-next. > > Wait, what? kvm/arm isn't in kvm-next? > > This will produce a needless clash with that, which is more important > than this cleanup. I'll rebase this as soon as that is merged. > > Christoffer, is there anything I can help with? > There are some worries about duplicating functionality on the ARM side of things. Specifically there are worries about the instruction decoding for the mmio instructions. My cycles are unfortunately too limited to change this right now and I'm also not sure I agree things will turn out nicer by unifying all decoding into a large complicated space ship, but it would be great if you could take a look. This discussion seems to be a good place to start: https://lists.cs.columbia.edu/pipermail/kvmarm/2012-September/003447.html Thanks! -Christoffer -- 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
