Michael Ellerman writes:
> On machines with 1TB segments and a 32-entry SLB it's quite hard to
> cause sufficient SLB pressure to trigger bugs caused due to badly
> timed SLB faults.
>
> We have seen this in the past and a few years ago added the
> disable_1tb_segments command line option to forc
Michael Ellerman's on January 19, 2019 8:27 pm:
> Michal Suchánek writes:
>
>> On Thu, 17 Jan 2019 23:13:28 +1100
>> Michael Ellerman wrote:
>>
>>> On machines with 1TB segments and a 32-entry SLB it's quite hard to
>>> cause sufficient SLB pressure to trigger bugs caused due to badly
>>> timed
Michal Suchánek writes:
> On Thu, 17 Jan 2019 23:13:28 +1100
> Michael Ellerman wrote:
>
>> On machines with 1TB segments and a 32-entry SLB it's quite hard to
>> cause sufficient SLB pressure to trigger bugs caused due to badly
>> timed SLB faults.
>>
>> We have seen this in the past and a few
On Thu, 17 Jan 2019 23:13:28 +1100
Michael Ellerman wrote:
> On machines with 1TB segments and a 32-entry SLB it's quite hard to
> cause sufficient SLB pressure to trigger bugs caused due to badly
> timed SLB faults.
>
> We have seen this in the past and a few years ago added the
> disable_1tb_s
On machines with 1TB segments and a 32-entry SLB it's quite hard to
cause sufficient SLB pressure to trigger bugs caused due to badly
timed SLB faults.
We have seen this in the past and a few years ago added the
disable_1tb_segments command line option to force the use of 256MB
segments. However e
