On 5/21/19 2:24 AM, Madhavan Srinivasan wrote:
>
> On 18/05/19 7:55 PM, Claudio Carvalho wrote:
>> From: Ram Pai When the ultravisor firmware is
>> available, it takes control over the LDBAR register. In this case,
>> thread-imc updates and save/restore operations on the LDBAR register are
>> ha
On 18/05/19 7:55 PM, Claudio Carvalho wrote:
From: Ram Pai When the ultravisor firmware is
available, it takes control over the LDBAR register. In this case,
thread-imc updates and save/restore operations on the LDBAR register
are handled by ultravisor.
we should remove the core and thread
On Sat, May 18, 2019 at 11:25:21AM -0300, Claudio Carvalho wrote:
> From: Ram Pai
>
> When the ultravisor firmware is available, it takes control over the
> LDBAR register. In this case, thread-imc updates and save/restore
> operations on the LDBAR register are handled by ultravisor.
>
> Signed-
From: Ram Pai
When the ultravisor firmware is available, it takes control over the
LDBAR register. In this case, thread-imc updates and save/restore
operations on the LDBAR register are handled by ultravisor.
Signed-off-by: Ram Pai
[Restrict LDBAR access in assembly code and some in C, update t
