[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 2/7] xen/nospec: Use always_inline to fix code gen for evaluate_nospec
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. 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. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |