Hi Mathieu,
On 05.09.2018 22:34, Mathieu Poirier wrote:
Hi Tomasz,
On Tue, Sep 04, 2018 at 04:20:34PM +0200, Tomasz Nowicki wrote:
For non-VHE systems host kernel runs at EL1 and jumps to EL2 whenever
hypervisor code should be executed. In this case ETM4x driver must
restrict configuration to
Hi Tomasz,
On Tue, Sep 04, 2018 at 04:20:34PM +0200, Tomasz Nowicki wrote:
> For non-VHE systems host kernel runs at EL1 and jumps to EL2 whenever
> hypervisor code should be executed. In this case ETM4x driver must
> restrict configuration to EL1 when it setups kernel tracing.
> However, there is
For non-VHE systems host kernel runs at EL1 and jumps to EL2 whenever
hypervisor code should be executed. In this case ETM4x driver must
restrict configuration to EL1 when it setups kernel tracing.
However, there is no separate hypervisor privilege level when VHE
is enabled, the host kernel runs at
3 matches
Mail list logo