> On Nov 12, 2018, at 2:53 AM, Martin Liška <mli...@suse.cz> wrote: > >> >> Okay, I see. >> >> I am also working on a similar option as yours, but make the -flive-patching >> as two level control: >> >> +flive-patching >> +Common RejectNegative Alias(flive-patching=,inline-clone) >> + >> +flive-patching= >> +Common Report Joined RejectNegative Enum(live_patching_level) >> Var(flag_live_patching) Init(LIVE_NONE) >> +-flive-patching=[inline-only-static|inline-clone] Control >> optimizations to provide a safe comp for live-patching purpose. >> >> the implementation for -flive-patching=inline-clone (the default) is exactly >> as yours, the new level -flive-patching=inline-only-static >> is to only enable inlining of static function for live patching, which is >> important for multiple-processes live patching to control memory >> consumption. >> >> (please see my 2nd version of the -flive-patching proposal). >> >> I will send out my complete patch in another email. > > Hi, sure, works for me. Let's make 2 level option.
thank you. I will send the patch tomorrow. Qing > > Martin
