From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58582) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bulO8-00013S-UR for qemu-devel@nongnu.org; Thu, 13 Oct 2016 15:09:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bulO4-0001zO-MJ for qemu-devel@nongnu.org; Thu, 13 Oct 2016 15:09:55 -0400 Received: from mail-pf0-x234.google.com ([2607:f8b0:400e:c00::234]:36540) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bulO4-0001yz-4F for qemu-devel@nongnu.org; Thu, 13 Oct 2016 15:09:52 -0400 Received: by mail-pf0-x234.google.com with SMTP id e6so38558434pfk.3 for ; Thu, 13 Oct 2016 12:09:52 -0700 (PDT) References: <1476301853-15774-1-git-send-email-thomas.hanson@linaro.org> From: Tom Hanson Message-ID: <57FFDBDC.1060201@linaro.org> Date: Thu, 13 Oct 2016 13:09:16 -0600 MIME-Version: 1.0 In-Reply-To: <1476301853-15774-1-git-send-email-thomas.hanson@linaro.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 0/4] target-arm: Handle tagged addresses when loading PC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, grant.likely@hpe.com 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