From: YunQiang Su <syq@debian.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Huacai Chen" <chenhuacai@gmail.com>,
"Huacai Chen" <zltjiangshi@gmail.com>,
"Thomas Huth" <thuth@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"BALATON Zoltan via" <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH V13 2/9] meson.build: Re-enable KVM support for MIPS
Date: Wed, 24 Mar 2021 10:12:08 +0800 [thread overview]
Message-ID: <CAKcpw6Ud2chjGLGmhr03pLd276d9A3eu-2pC0FLLfYcmg3UNqA@mail.gmail.com> (raw)
In-Reply-To: <16018289-0b28-4412-854b-0d30519588ca@www.fastmail.com>
Jiaxun Yang <jiaxun.yang@flygoat.com> 于2021年3月24日周三 上午9:29写道：
>
>
>
> On Tue, Mar 23, 2021, at 9:56 PM, Philippe Mathieu-Daudé wrote:
> > Hi Huacai,
> >
> > We are going to tag QEMU v6.0-rc0 today.
> >
> > I only have access to a 64-bit MIPS in little-endian to
> > test KVM.
> >
> > Can you test the other configurations please?
> > - 32-bit BE
> > - 32-bit LE
> > - 64-bit BE
>
How to run the test? just run a VM with KVM support on these kernel?
> +syq
> As Loongson doesn't have Big-Endian processor and Loongson 3A won't run 32bit kernel.
>
> Probably wecan test on boston or malta board?
>
> Thanks.
>
>
> >
> > Thanks!
> >
> > Phil.
> >
> >
> [...]
>
> --
> - Jiaxun
prev parent reply other threads:[~2021-03-24 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1602059975-10115-1-git-send-email-chenhc@lemote.com>
[not found] ` <1602059975-10115-3-git-send-email-chenhc@lemote.com>
[not found] ` <0dfbe14a-9ddb-0069-9d86-62861c059d12@amsat.org>
[not found] ` <CAAhV-H63zhXyUizwOxUtXdQQOR=r82493tgH8NfLmgXF0g8row@mail.gmail.com>
2020-11-20 10:55 ` [PATCH V13 2/9] meson.build: Re-enable KVM support for MIPS Philippe Mathieu-Daudé
2020-11-22 3:31 ` Huacai Chen
2021-03-23 13:56 ` Philippe Mathieu-Daudé
2021-03-24 1:22 ` Jiaxun Yang
2021-03-24 2:12 ` YunQiang Su [this message]
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=CAKcpw6Ud2chjGLGmhr03pLd276d9A3eu-2pC0FLLfYcmg3UNqA@mail.gmail.com \
--to=syq@debian.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@gmail.com \
--cc=f4bug@amsat.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=zltjiangshi@gmail.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).