From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Andreas Grapentin <gra@linux.ibm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Marc Zyngier <maz@kernel.org>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: arm64: Tolerate unused functions in extracted source
Date: Mon, 9 Nov 2026 10:37:04 +0100 [thread overview]
Message-ID: <8b6e2c2d-8d05-4bc8-9975-2f3cfb33d608@linux.ibm.com> (raw)
In-Reply-To: <20261105-series1-fixups2-v1-1-55f59e6c4c7b@linux.ibm.com>
Am 05.11.26 um 15:14 schrieb Andreas Grapentin:
> Extracting static declared arm64 functions with no consumer on the s390
> side into the generated sources causes compiler warnings when subsuming
> the generated sources from s390. This causes spurious compiler warnings
> that make it harder to extract larger, more cohesive portions of the
> arm64 source.
>
> Update the extraction logic to wrap the extracted source into diagnostic
> pragmas to disable -Wunused-function for the extracted block. This
> allows us to share more freely, and also opens up more paths for future
> code sharing with a separation of extraction and definition of consumers
> in separate commits.
>
> Obviously no functional change intended.
>
> Signed-off-by: Andreas Grapentin <gra@linux.ibm.com>
> Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
As you send this mail, I will drop Steffens signoff.
applied thanks.
> ---
> arch/s390/kvm/arm64/copy-arm64c.awk | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/arch/s390/kvm/arm64/copy-arm64c.awk b/arch/s390/kvm/arm64/copy-arm64c.awk
> index 640a7bcb7e23..a318be97c419 100644
> --- a/arch/s390/kvm/arm64/copy-arm64c.awk
> +++ b/arch/s390/kvm/arm64/copy-arm64c.awk
> @@ -42,6 +42,9 @@ BEGIN {
> print "#endif /* __INCL_GEN_ARM_FILE */"
> print "#undef __INCL_GEN_ARM_FILE"
> print ""
> + print "__diag_push()"
> + print "__diag_ignore_all(\"-Wunused-function\", \"tolerate unused functions shared from arm64\")"
> + print ""
>
> file_header_done = 1
> }
> @@ -78,5 +81,10 @@ copying {
> }
>
> END {
> - exit error || !found_marker || copying
> + ok = !error && found_marker && !copying
> + if (ok) {
> + print ""
> + print "__diag_pop()"
> + }
> + exit !ok
> }
>
> ---
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> change-id: 20261105-series1-fixups2-8ce6cc54a21f
>
> Best regards,
prev parent reply other threads:[~2026-11-09 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 14:14 Andreas Grapentin
2026-11-09 9:37 ` Christian Borntraeger [this message]
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=8b6e2c2d-8d05-4bc8-9975-2f3cfb33d608@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=maz@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=svens@linux.ibm.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
all inboxes | Powered by JetHome®