From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Bibo Mao" <maobibo@loongson.cn>, "Huacai Chen" <chenhuacai@kernel.org>
Cc: "Song Gao" <gaosong@loongson.cn>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"QEMU devel" <qemu-devel@nongnu.org>
Subject: Re: [RFC v3 1/2] target/loongarch: Add loongson binary translation feature
Date: Wed, 03 Jul 2024 18:19:46 +0800 [thread overview]
Message-ID: <c0d18ff3-3c58-4794-bc31-db6787e4becd@app.fastmail.com> (raw)
In-Reply-To: <5224f884-6327-f181-5bbf-f1d1f9f3b894@loongson.cn>
在2024年7月3日七月 下午6:10，maobibo写道：
[...]
>>>
>>> Huacai, would you agree with me?
>> For me the important thing is consistency, all vm-features or all
>> vcpu-features are both accepted.
> To understand features immediately is difficult job for me. There is
> supported features/used features usages etc, overall feature detection
> should be VM relative by my knowledge.
>
> Maybe after host machine type and migration feature detection and
> checking is finished, there will be further upstanding -:(
Do you agree with the scratch_vcpu approach? This seems to be the only
straight forward way to make some progress here.
Thanks
--
- Jiaxun
next prev parent reply other threads:[~2024-07-03 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 6:49 [RFC v3 0/2] target/loongarch: Add loongson binary translation feature Bibo Mao
2024-05-30 6:49 ` [RFC v3 1/2] " Bibo Mao
2024-07-01 6:57 ` Jiaxun Yang
2024-07-01 7:32 ` maobibo
2024-07-01 8:42 ` Jiaxun Yang
2024-07-01 9:23 ` maobibo
2024-07-03 7:50 ` Jiaxun Yang
2024-07-03 9:43 ` Huacai Chen
2024-07-03 10:10 ` maobibo
2024-07-03 10:19 ` Jiaxun Yang [this message]
2024-05-30 6:49 ` [RFC v3 2/2] target/loongarch: Implement lbt registers save/restore function Bibo Mao
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=c0d18ff3-3c58-4794-bc31-db6787e4becd@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=chenhuacai@kernel.org \
--cc=gaosong@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).