> > The upshot is that KVM_DEBUGREG_RELOAD is always set when returning > > from kvm_arch_vcpu_load() in stable, but not in Linus' tree. > > > > This happened because [0] and [1] are the same patch. [0] and [1] come > > from two > > different merges, and the later merge is trivially resolved; when [2] > > is applied it reverts both of them. Instead, when using the [1][2][0] > > order, patches applies normally but "KVM: x86: fix missed hardware > > breakpoints" is present in the final tree. > > > > Cc: stable kernels <stable@xxxxxxxxxxxxxxx> # 4.1, 4.4 > > Reported-by: Matt Fleming <matt@xxxxxxxxxxxxxxxxxxx> > > Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> > > Hey Paolo, > > Could you please confirm it's indeed a problem in 4.1? The current 4.1 tree > seems to be "correct" (the current code doesn't have the line that this > patch deletes). Hi Sasha, yes, 4.1 is good. It's limited to 4.4. Paolo -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html