On 29/10/2019 14:03, Jan Beulich wrote: > On 29.10.2019 14:46, Andrew Cooper wrote: >> If this patch series does not agreement, I will unblock livepatching on >> 4.13 by committing the v2 patch which causes BRANCH_HARDEN to depend on >> BROKEN and force it to be compiled out with no user choice at all. >> >> Unbreaking livepatching is strictly more important than keeping a brand >> new feature in 4.13 in a broken form. I've provided two alternative >> strategies to fix the 4.13 blockers, but if noone can agree on which >> approach to use, I will commit the simpler fix. > As to unblocking live patching - may I ask you look at the symbol > disambiguation patch I did submit? The thread here, as suggested > before, should now be solely about code generation.
Right, but the current state of l1tf-barrier is also a 4.13 blocker too - it is not in a shippable state. It either wants compiling out totally (the v2 patch), or having the code generation fixing (this v3 series), or some concrete 3rd suggestion. > And just in > case you've missed this: I did indicate I'm willing to give my > ack on the v3 patch here, provided you adjust the description as > asked for in my initial(?) reply. I had missed that, yes. I'll see about tweaking the commit message. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
