On 12 October 2016 at 20:50, Thomas Hanson wrote:
> If tagged addresses are enabled, then addresses being loaded into the
> PC must be cleaned up by overwriting the tag bits with either all 0's
> or all 1's as specified in the ARM ARM spec. The decision process is
> dependent on whether the code
On 13 October 2016 at 20:09, Tom Hanson wrote:
> Looking at arm_cpu_do_interrupt_aarch64() and the ARM spec, the
> new PC value is always an offset from the appropriate VBAR. The
> only place I can find the the VBAR being set is at boot time
> (i.e. UEFI).
Any guest system software can set the VB
On 10/12/2016 01:50 PM, Thomas Hanson wrote:
...
>
> Still looking into handling of tagged addresses for exceptions and
> exception returns. Will handle that as a separate patch set.
Peter,
Looking at arm_cpu_do_interrupt_aarch64() and the ARM spec, the new PC value is
always an offset fro
If tagged addresses are enabled, then addresses being loaded into the
PC must be cleaned up by overwriting the tag bits with either all 0's
or all 1's as specified in the ARM ARM spec. The decision process is
dependent on whether the code will be running in EL0/1 or in EL2/3 and
is controlled
