From: Andrew Jones <andrew.jones@linux.dev>
To: Nikos Nikoleris <nikos.nikoleris@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev, luc.maranget@inria.fr
Subject: Re: [kvm-unit-tests PATCH] arm64: Make vector_table and vector_stub weak symbols
Date: Thu, 18 May 2023 18:06:33 +0200 [thread overview]
Message-ID: <20230518-d8bd66e7bf671f5df706a216@orel> (raw)
In-Reply-To: <20230515221517.646549-1-nikos.nikoleris@arm.com>
On Mon, May 15, 2023 at 11:15:17PM +0100, Nikos Nikoleris wrote:
> This changes allows a test to define and override the declared symbols,
> taking control of the whole vector_table or a vector_stub.
Hi Nikos,
Can you add some motivation for this change to the commit message or
submit it along with some test that needs it?
Thanks,
drew
>
> Signed-off-by: Nikos Nikoleris <nikos.nikoleris@arm.com>
> ---
> arm/cstart64.S | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arm/cstart64.S b/arm/cstart64.S
> index e4ab7d06..eda0daa5 100644
> --- a/arm/cstart64.S
> +++ b/arm/cstart64.S
> @@ -275,8 +275,11 @@ exceptions_init:
> /*
> * Vector stubs
> * Adapted from arch/arm64/kernel/entry.S
> + * Declare as weak to allow external tests to redefine and override a
> + * vector_stub.
> */
> .macro vector_stub, name, vec
> +.weak \name
> \name:
> stp x0, x1, [sp, #-S_FRAME_SIZE]!
> stp x2, x3, [sp, #16]
> @@ -369,7 +372,13 @@ vector_stub el0_error_32, 15
> b \label
> .endm
>
> +
> +/*
> + * Declare as weak to allow external tests to redefine and override the
> + * default vector table.
> + */
> .align 11
> +.weak vector_table
> vector_table:
> ventry el1t_sync // Synchronous EL1t
> ventry el1t_irq // IRQ EL1t
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-05-18 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 22:15 [kvm-unit-tests PATCH] arm64: Make vector_table and vector_stub weak symbols Nikos Nikoleris
2023-05-18 16:06 ` Andrew Jones [this message]
2023-05-22 13:54 ` Nikos Nikoleris
2023-05-23 8:56 ` Andrew Jones
2023-05-23 9:52 ` Nikos Nikoleris
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=20230518-d8bd66e7bf671f5df706a216@orel \
--to=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=luc.maranget@inria.fr \
--cc=nikos.nikoleris@arm.com \
/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