From: Marc Zyngier <maz@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
Will Deacon <will@kernel.org>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
andre.przywara@arm.com, jean-philippe@linaro.org
Subject: Re: [RFC kvmtool 0/9] arm: Drop support for 32-bit kvmtool
Date: Mon, 17 Mar 2025 10:51:18 +0000 [thread overview]
Message-ID: <861puwnd5l.wl-maz@kernel.org> (raw)
In-Reply-To: <Z9f78K-m9h7YlzUr@raptor>
On Mon, 17 Mar 2025 10:39:44 +0000,
Alexandru Elisei <alexandru.elisei@arm.com> wrote:
>
> Hi Oliver,
>
> I'm CC'ing Marc and Andre (Andre is the only person that I know for a fact
> that ran 32 bit kvmtool).
>
> Haven't looked at the patches in detail, but as someone who ocassionally
> contributes to kvmtool, I have to say it's always nice to have fewer things
> to worry about. I, for one, never used 32 bit kvmtool, I just compiled for
> 32 bit arm to make sure it doesn't break.
>
> If nobody objects to dropping support for 32 bit kvmtool, I'm planning to
> review the patches.
Frankly, the removal of 32bit support is long overdue. Every time I
hack something in kvmtool (at least once a month), I have to wonder
how to fit that in the 32bit code that I *know* to be dead code.
We kept it ticking around when the kernel code was removed back in
5.6, and in the interval I have ran it *once*. These days, I don't
even have a working 32bit setup.
In all honesty, someone using 32bit KVM can also use an older build of
kvmtool (this piece of SW is *done*), and we can happily move on.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-03-17 10:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 22:25 [RFC kvmtool 0/9] arm: Drop support for 32-bit kvmtool Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 1/9] Drop support for 32-bit arm Oliver Upton
2025-03-20 16:58 ` Alexandru Elisei
2025-03-25 17:08 ` Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 2/9] arm64: Move arm64-only features into main directory Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 3/9] arm64: Combine kvm.c Oliver Upton
2025-03-20 16:59 ` Alexandru Elisei
2025-03-14 22:25 ` [RFC kvmtool 4/9] arm64: Merge kvm-cpu.c Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 5/9] arm64: Combine kvm-config-arch.h Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 6/9] arm64: Move remaining kvm/* headers Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 7/9] arm64: Move asm headers Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 8/9] arm64: Rename top-level directory Oliver Upton
2025-03-14 22:25 ` [RFC kvmtool 9/9] arm64: Get rid of the 'arm-common' include directory Oliver Upton
2025-03-20 17:01 ` Alexandru Elisei
2025-03-25 17:02 ` Oliver Upton
2025-03-17 10:39 ` [RFC kvmtool 0/9] arm: Drop support for 32-bit kvmtool Alexandru Elisei
2025-03-17 10:51 ` Marc Zyngier [this message]
2025-03-18 1:10 ` Oliver Upton
2025-03-19 14:18 ` Andre Przywara
2025-03-17 11:14 ` Marc Zyngier
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=861puwnd5l.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=jean-philippe@linaro.org \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.