From: Marc Zyngier <maz@kernel.org>
To: Andrew Jones <drjones@redhat.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
pbonzini@redhat.com, thuth@redhat.com, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] lib/devicetree: Support 64 bit addresses for the initrd
Date: Tue, 15 Feb 2022 09:26:13 +0000 [thread overview]
Message-ID: <87fsok4h1m.wl-maz@kernel.org> (raw)
In-Reply-To: <20220215073212.fp5lh4gfxk7clwwc@gator>
On Tue, 15 Feb 2022 07:32:12 +0000,
Andrew Jones <drjones@redhat.com> wrote:
>
> On Mon, Feb 14, 2022 at 05:01:40PM +0000, Marc Zyngier wrote:
> > Hi all,
> >
> > On Mon, 14 Feb 2022 16:20:13 +0000,
> > Alexandru Elisei <alexandru.elisei@arm.com> wrote:
> > >
> > > Hi Drew,
> > >
> > > (CC'ing Marc, he know more about 32 bit guest support than me)
> > >
> > > On Mon, Feb 14, 2022 at 03:24:44PM +0100, Andrew Jones wrote:
> > > > I'm not sure it's worth adding another patch on top for that now, though.
> > > > By the lack of new 32-bit arm unit tests getting submitted, I'm not even
> > > > sure it's worth maintaining 32-bit arm at all...
> > >
> > > As far as I know, 32 bit guests are still very much supported and
> > > maintained for KVM, so I think it would still be very useful to have the
> > > tests.
> >
> > I can't force people to write additional tests (or even start writing
> > the first one), but I'd like to reaffirm that AArch32 support still is
> > a first class citizen when it comes to KVM/arm64.
> >
> > It has been tremendously useful even in the very recent past to debug
> > issues that were plaguing bare metal Linux, and i don't plan to get
> > rid of it anytime soon (TBH, it is too small to even be noticeable).
> >
>
> OK, let's keep 32-bit arm support in kvm-unit-tests, at least as long as
> we can find hardware to test it with (I still have access to a mustang).
That HW will be with us for a *very* long time, given how popular
things like A53 and A72 have been (and still are).
> Does kvmtool support launching AArch32 guests? If so, then I suppose we
> should also test kvmtool + 32-bit arm kvm-unit-tests.
It does. Passing --aarch32 as a parameter results in AArch32 EL1 being
selected. The only thing that doesn't work with kvmtool and this flag
is the kvmtool-provided init when booting a 32bit kernel directly (we
only carry a 64bit version). This should not affect unit tests, which
are standalone.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-02-15 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 12:05 [kvm-unit-tests PATCH] lib/devicetree: Support 64 bit addresses for the initrd Alexandru Elisei
2022-02-14 13:52 ` Andrew Jones
2022-02-14 14:06 ` Alexandru Elisei
2022-02-14 14:24 ` Andrew Jones
2022-02-14 16:20 ` Alexandru Elisei
2022-02-14 16:36 ` Andrew Jones
2022-02-14 17:01 ` Marc Zyngier
2022-02-15 7:32 ` Andrew Jones
2022-02-15 9:26 ` Marc Zyngier [this message]
2022-02-15 10:07 ` Alexandru Elisei
2022-02-15 12:53 ` Andrew Jones
2022-02-15 14:16 ` Alexandru Elisei
2022-02-15 15:22 ` Alexandru Elisei
2022-02-15 15:53 ` Andrew Jones
2022-02-15 15:50 ` Andrew Jones
2022-02-15 16:15 ` Alexandru Elisei
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=87fsok4h1m.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@redhat.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 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.