On 10/14/2015 12:40 AM, Sergey Fedorov wrote:
Otherwise, "!(tb_end <= start || tb_start >= end)" condition
check will fail
...
So we either
need to change the condition in tb_invalidate_phys_page_range() or do
the PC advancement trick during translation, no matter can instructions
cross a page boundary or not.
I think you're right.
The reason I've not seen an issue so far is that breakpoint_invalidate expands
the requested range to the entire page. So the failure to invalidate would
require the breakpoint to be at the page boundary.
r~
