From: Sebastian Ott <sebott@redhat.com>
To: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH 0/3] KVM: arm64: fix warnings in W=1 build
Date: Fri, 12 Jul 2024 13:03:29 +0200 [thread overview]
Message-ID: <20240712110332.10970-1-sebott@redhat.com> (raw)
Building arch/arm64/kvm/ with W=1 spills out a lot of warnings. When
changing stuff I try to use as much tooling as possible to make sure
that I don't screw up - having a clean baseline imho helps with that.
With the first 2 patches applied make W=1 arch/arm64/kvm/ runs without
warnings for me (fedora userspace, kvm-arm/next). Patch 3 gets rid
of sparse lock warnings in arch/arm64/kvm/vgic/.
Sebastian Ott (3):
KVM: arm64: fix override-init warnings in W=1 builds
KVM: arm64: fix kdoc warnings in W=1 builds
KVM: arm64: vgic: fix unexpected unlock sparse warnings
arch/arm64/kvm/arm.c | 1 +
arch/arm64/kvm/handle_exit.c | 5 +++++
arch/arm64/kvm/hyp/nvhe/switch.c | 6 ++----
arch/arm64/kvm/hyp/vhe/switch.c | 3 +--
arch/arm64/kvm/sys_regs.c | 5 +++++
arch/arm64/kvm/vgic/vgic-irqfd.c | 7 ++++---
arch/arm64/kvm/vgic/vgic-its.c | 18 +++++++++++-------
arch/arm64/kvm/vgic/vgic-v3.c | 2 +-
arch/arm64/kvm/vgic/vgic.c | 2 +-
arch/arm64/kvm/vgic/vgic.h | 2 +-
10 files changed, 32 insertions(+), 19 deletions(-)
--
2.42.0
next reply other threads:[~2024-07-12 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 11:03 Sebastian Ott [this message]
2024-07-12 11:03 ` [PATCH 1/3] KVM: arm64: fix override-init warnings in W=1 builds Sebastian Ott
2024-07-12 21:55 ` Marc Zyngier
2024-07-15 9:35 ` Mark Rutland
2024-07-15 10:43 ` Sebastian Ott
2024-07-15 10:28 ` Sebastian Ott
2024-07-15 14:40 ` Marc Zyngier
2024-07-12 11:03 ` [PATCH 2/3] KVM: arm64: fix kdoc " Sebastian Ott
2024-07-12 11:03 ` [PATCH 3/3] KVM: arm64: vgic: fix unexpected unlock sparse warnings Sebastian Ott
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=20240712110332.10970-1-sebott@redhat.com \
--to=sebott@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).