From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, julien@xen.org, bertrand.marquis@arm.com,
michal.orzel@amd.com, Volodymyr_Babchuk@epam.com,
jbeulich@suse.com, andrew.cooper3@citrix.com,
edgar.iglesias@amd.com
Subject: [PATCH v3 3/9] xen/arm64: sve: Add missing code symbol annotations
Date: Wed, 1 May 2024 05:54:42 +0200 [thread overview]
Message-ID: <20240501035448.964625-4-edgar.iglesias@gmail.com> (raw)
In-Reply-To: <20240501035448.964625-1-edgar.iglesias@gmail.com>
From: "Edgar E. Iglesias" <edgar.iglesias@amd.com>
Use the generic xen/linkage.h macros to annotate code symbols
and add missing annotations.
Signed-off-by: Edgar E. Iglesias <edgar.iglesias@amd.com>
---
xen/arch/arm/arm64/sve-asm.S | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/xen/arch/arm/arm64/sve-asm.S b/xen/arch/arm/arm64/sve-asm.S
index 59dbefbbb2..2d8b895f07 100644
--- a/xen/arch/arm/arm64/sve-asm.S
+++ b/xen/arch/arm/arm64/sve-asm.S
@@ -161,9 +161,10 @@
.endm
/* Gets the current vector register size in bytes */
-GLOBAL(sve_get_hw_vl)
+FUNC(sve_get_hw_vl)
_sve_rdvl 0, 1
ret
+END(sve_get_hw_vl)
/*
* Save the SVE context
@@ -172,9 +173,10 @@ GLOBAL(sve_get_hw_vl)
* x1 - pointer to buffer for P0-15
* x2 - Save FFR if non-zero
*/
-GLOBAL(sve_save_ctx)
+FUNC(sve_save_ctx)
sve_save 0, 1, x2
ret
+END(sve_save_ctx)
/*
* Load the SVE context
@@ -183,9 +185,10 @@ GLOBAL(sve_save_ctx)
* x1 - pointer to buffer for P0-15
* x2 - Restore FFR if non-zero
*/
-GLOBAL(sve_load_ctx)
+FUNC(sve_load_ctx)
sve_load 0, 1, x2
ret
+END(sve_load_ctx)
/*
* Local variables:
--
2.40.1
next prev parent reply other threads:[~2024-05-02 17:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 3:54 [PATCH v3 0/9] xen/arm: arm64: Annotate code symbols Edgar E. Iglesias
2024-05-01 3:54 ` [PATCH v3 1/9] xen/arm64: entry: Add missing code symbol annotations Edgar E. Iglesias
2024-05-01 3:54 ` [PATCH v3 2/9] xen/arm64: smc: " Edgar E. Iglesias
2024-05-03 23:30 ` Stefano Stabellini
2024-05-01 3:54 ` Edgar E. Iglesias [this message]
2024-05-03 23:30 ` [PATCH v3 3/9] xen/arm64: sve: " Stefano Stabellini
2024-05-01 3:54 ` [PATCH v3 4/9] xen/arm64: head: " Edgar E. Iglesias
2024-05-03 23:56 ` Stefano Stabellini
2024-05-06 12:49 ` Edgar E. Iglesias
2024-05-01 3:54 ` [PATCH v3 5/9] xen/arm64: debug: " Edgar E. Iglesias
2024-05-03 23:56 ` Stefano Stabellini
2024-05-01 3:54 ` [PATCH v3 6/9] xen/arm64: bpi: " Edgar E. Iglesias
2024-05-04 0:14 ` Stefano Stabellini
2024-05-06 12:54 ` Edgar E. Iglesias
2024-05-07 9:57 ` Julien Grall
2024-05-07 16:55 ` Edgar E. Iglesias
2024-05-07 17:37 ` Julien Grall
2024-05-10 16:26 ` Edgar E. Iglesias
2024-05-14 7:17 ` Jan Beulich
2024-05-01 3:54 ` [PATCH v3 7/9] xen/arm64: mmu/head: " Edgar E. Iglesias
2024-05-04 0:15 ` Stefano Stabellini
2024-05-01 3:54 ` [PATCH v3 8/9] xen/arm64: cache: Use the generic xen/linkage.h macros Edgar E. Iglesias
2024-05-04 0:15 ` Stefano Stabellini
2024-05-01 3:54 ` [PATCH v3 9/9] xen/arm64: lib: " Edgar E. Iglesias
2024-05-04 0:16 ` Stefano Stabellini
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=20240501035448.964625-4-edgar.iglesias@gmail.com \
--to=edgar.iglesias@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=edgar.iglesias@amd.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).