On Mon, Nov 26, 2018 at 11:11:53 +, Alex Bennée wrote:
>
> Emilio G. Cota writes:
>
> > On Thu, Nov 22, 2018 at 17:09:22 +, Alex Bennée wrote:
> >>
> >> Emilio G. Cota writes:
> >>
> >> > This will be used by plugin code to flush the code cache as well
> >> > as doing other bookkeeping
Emilio G. Cota writes:
> On Thu, Nov 22, 2018 at 17:09:22 +, Alex Bennée wrote:
>>
>> Emilio G. Cota writes:
>>
>> > This will be used by plugin code to flush the code cache as well
>> > as doing other bookkeeping in a safe work environment.
>>
>> This seems a little excessive given the
On Thu, Nov 22, 2018 at 17:09:22 +, Alex Bennée wrote:
>
> Emilio G. Cota writes:
>
> > This will be used by plugin code to flush the code cache as well
> > as doing other bookkeeping in a safe work environment.
>
> This seems a little excessive given the plugin code could just call
>
Emilio G. Cota writes:
> This will be used by plugin code to flush the code cache as well
> as doing other bookkeeping in a safe work environment.
This seems a little excessive given the plugin code could just call
tb_flush() directly. Wouldn't calling tb_flush after scheduling the
