From: Tom Hanson <thomas.hanson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, grant.likely@hpe.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] target-arm: Handle tagged addresses when loading PC
Date: Thu, 13 Oct 2016 13:09:16 -0600 [thread overview]
Message-ID: <57FFDBDC.1060201@linaro.org> (raw)
In-Reply-To: <1476301853-15774-1-git-send-email-thomas.hanson@linaro.org>
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 from the appropriate VBAR. The only place I can find the the VBAR being set is at boot time (i.e. UEFI).
Can the boot code use a tagged pointer to specify the VBAR?
Is there some other place/time when the VBAR can be modified post-boot?
Thanks,
Tom
next prev parent reply other threads:[~2016-10-13 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 19:50 [Qemu-devel] [PATCH v3 0/4] target-arm: Handle tagged addresses when loading PC Thomas Hanson
2016-10-12 19:50 ` [Qemu-devel] [PATCH v3 1/4] target-arm: Infrastucture changes to enable handling of tagged address loading into PC Thomas Hanson
2016-10-12 19:50 ` [Qemu-devel] [PATCH v3 2/4] target-arm: Code changes to implement overwrite of tag field on PC load Thomas Hanson
2016-10-12 19:50 ` [Qemu-devel] [PATCH v3 3/4] target-arm: Comments to mark location of pending work for 56 bit addresses Thomas Hanson
2016-10-12 19:50 ` [Qemu-devel] [PATCH v3 4/4] target-arm: Comments added to identify cases in a switch Thomas Hanson
2016-10-13 19:09 ` Tom Hanson [this message]
2016-10-13 21:14 ` [Qemu-devel] [PATCH v3 0/4] target-arm: Handle tagged addresses when loading PC Peter Maydell
2016-10-17 17:29 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57FFDBDC.1060201@linaro.org \
--to=thomas.hanson@linaro.org \
--cc=grant.likely@hpe.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).