From: Tony Lindgren <tony@atomide.com>
To: Michael Mrozek <EvilDragon@openpandora.org>
Cc: Marc Zyngier <maz@kernel.org>, Lukas Straub <lukasstraub2@web.de>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel@pyra-handheld.com
Subject: Re: Against removing aarch32 kvm host support
Date: Tue, 28 Apr 2020 09:26:11 -0700 [thread overview]
Message-ID: <20200428162611.GW43721@atomide.com> (raw)
In-Reply-To: <9c67a3722611d1ec9fe1e8a1fbe65956b32147c3.camel@openpandora.org>
* Michael Mrozek <EvilDragon@openpandora.org> [200428 14:27]:
> Am Dienstag, den 28.04.2020, 14:30 +0100 schrieb Marc Zyngier:
> I know we have to accept the decision, but so far, I've known Linux to support
> as many older devices as possible as well - removing KVM Host 32bit support
> would be a step back here.
>
> Is there a specific reason for that?
> Is it too complex to maintain alongside the aarch64 KVM Host?
I don't know the details, but ideally things would be set up
in a way where folks interested in patching 32-bit arm kvm support
can do so without causing issues for 64-bit kvm development.
That being said, I don't know who might be interested in doing
all the work for that. It's unrealistic to expect Marc to do this
work if he's not using it.
Features that are used get more resources, and features that are
less used end up just bitrotting into a broken state in about
six weeks in the Linux kernel :)
Regards,
Tony
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Michael Mrozek <EvilDragon@openpandora.org>
Cc: Marc Zyngier <maz@kernel.org>, Lukas Straub <lukasstraub2@web.de>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel@pyra-handheld.com
Subject: Re: Against removing aarch32 kvm host support
Date: Tue, 28 Apr 2020 09:26:11 -0700 [thread overview]
Message-ID: <20200428162611.GW43721@atomide.com> (raw)
In-Reply-To: <9c67a3722611d1ec9fe1e8a1fbe65956b32147c3.camel@openpandora.org>
* Michael Mrozek <EvilDragon@openpandora.org> [200428 14:27]:
> Am Dienstag, den 28.04.2020, 14:30 +0100 schrieb Marc Zyngier:
> I know we have to accept the decision, but so far, I've known Linux to support
> as many older devices as possible as well - removing KVM Host 32bit support
> would be a step back here.
>
> Is there a specific reason for that?
> Is it too complex to maintain alongside the aarch64 KVM Host?
I don't know the details, but ideally things would be set up
in a way where folks interested in patching 32-bit arm kvm support
can do so without causing issues for 64-bit kvm development.
That being said, I don't know who might be interested in doing
all the work for that. It's unrealistic to expect Marc to do this
work if he's not using it.
Features that are used get more resources, and features that are
less used end up just bitrotting into a broken state in about
six weeks in the Linux kernel :)
Regards,
Tony
next prev parent reply other threads:[~2020-04-28 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 12:38 Against removing aarch32 kvm host support Lukas Straub
2020-04-28 12:38 ` Lukas Straub
2020-04-28 13:30 ` Marc Zyngier
2020-04-28 13:30 ` Marc Zyngier
2020-04-28 14:26 ` Michael Mrozek
2020-04-28 14:26 ` Michael Mrozek
2020-04-28 16:26 ` Tony Lindgren [this message]
2020-04-28 16:26 ` Tony Lindgren
2020-04-28 16:39 ` Marc Zyngier
2020-04-28 16:39 ` 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=20200428162611.GW43721@atomide.com \
--to=tony@atomide.com \
--cc=EvilDragon@openpandora.org \
--cc=kernel@pyra-handheld.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lukasstraub2@web.de \
--cc=maz@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.