On 12.12.2020 17:31, Richard Henderson wrote:
On 12/12/20 12:22 AM, Pavel Dovgalyuk wrote:
However, we can't cache them directly, because hash table can include only one
block with the specific pc.
That's not true at all.
Thanks, I missed, that icount is used for TB comparison in hash
On 12/12/20 12:22 AM, Pavel Dovgalyuk wrote:
> However, we can't cache them directly, because hash table can include only one
> block with the specific pc.
That's not true at all.
r~
On 12.12.2020 00:41, Richard Henderson wrote:
On 12/8/20 3:10 AM, Pavel Dovgalyuk wrote:
cpu-exec tries to execute TB without caching when current
icount budget is over. But sometimes refilled budget is big
enough to try executing cached blocks.
This patch checks that instruction budget is big
On 12/8/20 3:10 AM, Pavel Dovgalyuk wrote:
> cpu-exec tries to execute TB without caching when current
> icount budget is over. But sometimes refilled budget is big
> enough to try executing cached blocks.
> This patch checks that instruction budget is big enough
> for next block execution instead
On 08/12/20 10:10, Pavel Dovgalyuk wrote:
cpu-exec tries to execute TB without caching when current
icount budget is over. But sometimes refilled budget is big
enough to try executing cached blocks.
This patch checks that instruction budget is big enough
for next block execution instead of just
cpu-exec tries to execute TB without caching when current
icount budget is over. But sometimes refilled budget is big
enough to try executing cached blocks.
This patch checks that instruction budget is big enough
for next block execution instead of just running cpu_exec_nocache.
It halves the
