On 04/26/2019 09:04 AM, Joe Lawrence wrote: > On 4/26/19 11:40 AM, Mario Smarduch wrote: >> >> >> On 04/26/2019 06:32 AM, Joe Lawrence wrote: ndicator to the new code that patching is complete. .... > > > If you can share the source .patch or upstream commit id, that would be > helpful, but I can understand if that needs to remain confidential for > security reasons. > > Hope this helps, > > -- Joe A side question regarding calling the new function after it's patched and performance. Is the similar trampoline mechanism used when a ftrace hook is set? Meaning pt_regs is presented to hook and 'rip' is changed? - Mairo _______________________________________________ kpatch mailing list [email protected] https://www.redhat.com/mailman/listinfo/kpatch
- [kpatch] livepatch vs kpatch hooks and stack check Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks and stack ch... Joe Lawrence
- Re: [kpatch] livepatch vs kpatch hooks and stac... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks and ... Joe Lawrence
- Re: [kpatch] livepatch vs kpatch hooks ... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks ... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch h... Joe Lawrence
- Re: [kpatch] livepatch vs kpat... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks and stac... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks and ... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks ... Joe Lawrence
- Re: [kpatch] livepatch vs kpatch hooks and stac... Evgenii Shatokhin
- Re: [kpatch] livepatch vs kpatch hooks and ... Mario Smarduch
- Re: [kpatch] livepatch vs kpatch hooks ... Evgenii Shatokhin
