From: Arnd Bergmann <arnd@arndb.de>
To: Olof Johansson <olof@lixom.net>
Cc: Anders Berg <anders.berg@lsi.com>,
Russell King <linux@arm.linux.org.uk>,
kvm list <kvm@vger.kernel.org>, Marc Zyngier <maz@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Will Deacon <will@kernel.org>,
kvmarm@lists.cs.columbia.edu,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 0/5] Removing support for 32bit KVM/arm host
Date: Mon, 10 Feb 2020 16:54:52 +0100 [thread overview]
Message-ID: <CAK8P3a1pi3yBVMdXQyZsm_NFLn=UrVRgQ2O5b3-RmF9JTi5z7A@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMhHkez-5vxwWuzXc2Rm=dYYWjMX9C8AewVy9GDWuZcwMw@mail.gmail.com>
On Mon, Feb 10, 2020 at 4:32 PM Olof Johansson <olof@lixom.net> wrote:
> On Mon, Feb 10, 2020 at 3:13 PM Marc Zyngier <maz@kernel.org> wrote:
> >
> > KVM/arm was merged just over 7 years ago, and has lived a very quiet
> > life so far. It mostly works if you're prepared to deal with its
> > limitations, it has been a good prototype for the arm64 version,
> > but it suffers a few problems:
> >
> > - It is incomplete (no debug support, no PMU)
> > - It hasn't followed any of the architectural evolutions
> > - It has zero users (I don't count myself here)
> > - It is more and more getting in the way of new arm64 developments
> >
> > So here it is: unless someone screams and shows that they rely on
> > KVM/arm to be maintained upsteam, I'll remove 32bit host support
> > form the tree. One of the reasons that makes me confident nobody is
> > using it is that I never receive *any* bug report. Yes, it is perfect.
> > But if you depend on KVM/arm being available in mainline, please shout.
> >
> > To reiterate: 32bit guest support for arm64 stays, of course. Only
> > 32bit host goes. Once this is merged, I plan to move virt/kvm/arm to
> > arm64, and cleanup all the now unnecessary abstractions.
I think this makes a lot of sense: we are seeing fewer new 32-bit
systems that have enough RAM to be a usable virtualization host,
as most new boards with more than 1GB of RAM typically pick 64-bit
SoCs, and on less than 1GB it gets awfully tight to do anything useful.
> Since I'm generally happy to drop legacy code that has no users, with
> the "if there are any significant users that speak up, I'll revoke my
> support" caveat:
>
> Acked-by: Olof Johansson <olof@lixom.net>
Same here
Acked-by: Arnd Bergmann <arnd@arndb.de>
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-02-10 15:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200210141344eucas1p25a6da0b0251931ef3659397a6f34c0c3@eucas1p2.samsung.com>
2020-02-10 14:13 ` [RFC PATCH 0/5] Removing support for 32bit KVM/arm host Marc Zyngier
2020-02-10 14:13 ` [RFC PATCH 1/5] arm: Unplug KVM from the build system Marc Zyngier
2020-02-10 14:13 ` [RFC PATCH 2/5] arm: Remove KVM from config files Marc Zyngier
2020-02-10 14:13 ` [RFC PATCH 3/5] arm: Remove 32bit KVM host support Marc Zyngier
2020-02-10 14:13 ` [RFC PATCH 4/5] arm: Remove HYP/Stage-2 page-table support Marc Zyngier
2020-02-10 14:13 ` [RFC PATCH 5/5] arm: Remove GICv3 vgic compatibility macros Marc Zyngier
2020-02-10 15:21 ` [RFC PATCH 0/5] Removing support for 32bit KVM/arm host Olof Johansson
2020-02-10 15:54 ` Arnd Bergmann [this message]
2020-02-10 15:46 ` Will Deacon
2020-02-10 16:25 ` Russell King - ARM Linux admin
2020-02-10 16:26 ` Russell King - ARM Linux admin
2020-02-11 15:12 ` Vladimir Murzin
2020-02-11 15:23 ` Catalin Marinas
2020-02-17 0:14 ` Linus Walleij
2020-02-19 13:53 ` Stefan Agner
2020-02-20 11:01 ` Marc Zyngier
2020-02-19 14:56 ` Christoffer Dall
2020-02-19 15:09 ` Arnd Bergmann
2020-02-19 15:46 ` Jan Kiszka
2020-02-20 10:29 ` Marc Zyngier
2020-02-20 12:44 ` Marek Szyprowski
2020-02-20 13:15 ` Marc Zyngier
2020-02-20 13:17 ` Paolo Bonzini
2020-02-20 13:32 ` Robin Murphy
2020-02-20 14:01 ` Marc Zyngier
2020-02-20 14:38 ` Robin Murphy
2020-02-22 14:21 ` Takashi Yoshi
2020-02-22 14:40 ` Takashi Yoshi
2020-02-22 21:31 ` Arnd Bergmann
2020-02-25 21:34 ` Takashi Yoshi
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='CAK8P3a1pi3yBVMdXQyZsm_NFLn=UrVRgQ2O5b3-RmF9JTi5z7A@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=anders.berg@lsi.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=maz@kernel.org \
--cc=olof@lixom.net \
--cc=pbonzini@redhat.com \
--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 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).