From: Peter Xu <peterx@redhat.com>
To: maobibo <maobibo@loongson.cn>
Cc: Song Gao <gaosong@loongson.cn>, Fabiano Rosas <farosas@suse.de>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 5/5] tests: Add migration test for loongarch64
Date: Wed, 21 Feb 2024 12:14:11 +0800 [thread overview]
Message-ID: <ZdV4k4rckpV7bjRx@x1n> (raw)
In-Reply-To: <2c298d69-f7d2-829f-c700-e6d6e1f86080@loongson.cn>
On Wed, Feb 21, 2024 at 11:47:27AM +0800, maobibo wrote:
> Now loongarch virt machine type is not full-featured, it will be long-term
> issue to keep compatible ability access different qemu versions or kernel
> versions. It is a big challenge for us, now the main purpose of migration
> test is that it can check whether modification with kvm mmu part is correct
> or not.
That's fine then. Feel free to pick this patch up through the loongarch64
branch when ready. Thanks.
--
Peter Xu
next prev parent reply other threads:[~2024-02-21 4:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 12:41 [PATCH 0/5] Add migration test for loongarch64 Bibo Mao
2024-02-20 12:41 ` [PATCH 1/5] hw/loongarch: Rename LOONGARCH_MACHINE with VIRT_MACHINE Bibo Mao
2024-02-20 12:41 ` [PATCH 2/5] hw/loongarch: Rename LoongArchMachineState with VirtMachineState Bibo Mao
2024-02-20 12:41 ` [PATCH 3/5] hw/loongarch: Add compat machine for 9.0 Bibo Mao
2024-03-04 8:40 ` gaosong
2024-02-20 12:41 ` [PATCH 4/5] hw/loongarch: Set minimium memory size as 256M Bibo Mao
2024-02-20 16:47 ` Thomas Huth
2024-02-21 1:52 ` maobibo
2024-02-20 12:41 ` [PATCH 5/5] tests: Add migration test for loongarch64 Bibo Mao
2024-02-20 16:49 ` Thomas Huth
2024-02-21 3:01 ` Peter Xu
[not found] ` <2c298d69-f7d2-829f-c700-e6d6e1f86080@loongson.cn>
2024-02-21 4:14 ` Peter Xu [this message]
2024-02-21 21:24 ` Fabiano Rosas
2024-02-22 1:57 ` maobibo
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=ZdV4k4rckpV7bjRx@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=gaosong@loongson.cn \
--cc=lvivier@redhat.com \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--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 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).