Matt Evans writes:
>> On 28 Mar 2018, at 11:36, Matt Evans wrote:
>>> On 28 Mar 2018, at 06:54, Michael Ellerman wrote:
>>> Matt Evans writes:
When using SIG_DBG_BRANCH_TRACING, MSR.BE is left enabled in the
user context when single_step_exception() prepares the SIGTRAP
delivery.
On Mon, 2018-03-26 at 16:55:21 UTC, Matt Evans wrote:
> When using SIG_DBG_BRANCH_TRACING, MSR.BE is left enabled in the
> user context when single_step_exception() prepares the SIGTRAP
> delivery. The resulting branch-trap-within-the-SIGTRAP-handler
> isn't healthy.
>
> Commit 2538c2d08f46141550
Hi Michael,
> On 28 Mar 2018, at 11:36, Matt Evans wrote:
>
> Howdy Michael,
>
>> On 28 Mar 2018, at 06:54, Michael Ellerman wrote:
>>
>> Matt Evans writes:
>>
>>> When using SIG_DBG_BRANCH_TRACING, MSR.BE is left enabled in the
>>> user context when single_step_exception() prepares the SIG
Howdy Michael,
> On 28 Mar 2018, at 06:54, Michael Ellerman wrote:
>
> Matt Evans writes:
>
>> When using SIG_DBG_BRANCH_TRACING, MSR.BE is left enabled in the
>> user context when single_step_exception() prepares the SIGTRAP
>> delivery. The resulting branch-trap-within-the-SIGTRAP-handler
>
Matt Evans writes:
> When using SIG_DBG_BRANCH_TRACING, MSR.BE is left enabled in the
> user context when single_step_exception() prepares the SIGTRAP
> delivery. The resulting branch-trap-within-the-SIGTRAP-handler
> isn't healthy.
>
> Commit 2538c2d08f46141550a1e68819efa8fe31c6e3dc broke this,
When using SIG_DBG_BRANCH_TRACING, MSR.BE is left enabled in the
user context when single_step_exception() prepares the SIGTRAP
delivery. The resulting branch-trap-within-the-SIGTRAP-handler
isn't healthy.
Commit 2538c2d08f46141550a1e68819efa8fe31c6e3dc broke this, by
replacing an MSR mask operat