Re: [PATCH 1/2] exec: flush CPU TB cache in breakpoint_invalidate

2020-02-05 Thread Max Filippov
On Wed, Feb 5, 2020 at 3:00 AM Richard Henderson wrote: > > On 11/27/19 10:06 PM, Max Filippov wrote: > > When a breakpoint is inserted at location for which there's currently no > > virtual to physical translation no action is taken on CPU TB cache. If a > > TB for that virtual address already ex

Re: [PATCH 1/2] exec: flush CPU TB cache in breakpoint_invalidate

2020-02-05 Thread Richard Henderson
On 11/27/19 10:06 PM, Max Filippov wrote: > When a breakpoint is inserted at location for which there's currently no > virtual to physical translation no action is taken on CPU TB cache. If a > TB for that virtual address already exists but is not visible ATM the > breakpoint won't be hit next time

Re: [PATCH 1/2] exec: flush CPU TB cache in breakpoint_invalidate

2019-12-03 Thread Alex Bennée
Richard Henderson writes: > On 11/27/19 10:06 PM, Max Filippov wrote: >> When a breakpoint is inserted at location for which there's currently no >> virtual to physical translation no action is taken on CPU TB cache. If a >> TB for that virtual address already exists but is not visible ATM the

Re: [PATCH 1/2] exec: flush CPU TB cache in breakpoint_invalidate

2019-12-01 Thread Richard Henderson
On 11/27/19 10:06 PM, Max Filippov wrote: > When a breakpoint is inserted at location for which there's currently no > virtual to physical translation no action is taken on CPU TB cache. If a > TB for that virtual address already exists but is not visible ATM the > breakpoint won't be hit next time

[PATCH 1/2] exec: flush CPU TB cache in breakpoint_invalidate

2019-11-27 Thread Max Filippov
When a breakpoint is inserted at location for which there's currently no virtual to physical translation no action is taken on CPU TB cache. If a TB for that virtual address already exists but is not visible ATM the breakpoint won't be hit next time an instruction at that address will be executed.