Hello Suzuki,
On 3/2/21 10:01 AM, Suzuki K Poulose wrote:
> Hi Alex
>
> On 3/1/21 4:32 PM, Alexandru Elisei wrote:
>> Hello Suzuki,
>>
>> On 2/25/21 7:35 PM, Suzuki K Poulose wrote:
>>> The nvhe hyp saves the SPE context, flushing any unwritten
>>
>> Perhaps that can be reworded to "The nVHE world
Hi Alex
On 3/1/21 4:32 PM, Alexandru Elisei wrote:
Hello Suzuki,
On 2/25/21 7:35 PM, Suzuki K Poulose wrote:
The nvhe hyp saves the SPE context, flushing any unwritten
Perhaps that can be reworded to "The nVHE world switch code saves [..]".
Sure
Also, according to my understanding of "c
Hi Suzuki,
On 2021-03-02 10:01, Suzuki K Poulose wrote:
Hi Alex
On 3/1/21 4:32 PM, Alexandru Elisei wrote:
Hello Suzuki,
On 2/25/21 7:35 PM, Suzuki K Poulose wrote:
The nvhe hyp saves the SPE context, flushing any unwritten
Perhaps that can be reworded to "The nVHE world switch code saves
Hello Suzuki,
On 2/25/21 7:35 PM, Suzuki K Poulose wrote:
> The nvhe hyp saves the SPE context, flushing any unwritten
Perhaps that can be reworded to "The nVHE world switch code saves [..]".
Also, according to my understanding of "context", that means saving *all* the
related registers. But KVM
The nvhe hyp saves the SPE context, flushing any unwritten
data before we switch to the guest. But this operation is
performed way too late, because :
- The ownership of the SPE is transferred to EL2. i.e,
using EL2 translations. (MDCR_EL2_E2PB == 0)
- The guest Stage1 is loaded.
Thus the
5 matches
Mail list logo