qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: 方 <1584389042@qq.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Assessment of the difficulty in porting CPU architecture for qemu
Date: Thu, 15 Feb 2024 10:37:57 +0000	[thread overview]
Message-ID: <CAFEAcA8grC+Mi9LcNPPXqJUCVNp1a6PcEWX0nUDsOe14ARgwbw@mail.gmail.com> (raw)
In-Reply-To: <tencent_29796A8EF3E655396E27566AC5CE1103A509@qq.com>

On Fri, 17 Nov 2023 at 07:35, 方 <1584389042@qq.com> wrote:
>
>  Hello everyone! I am working on implementing a tool to assess the complexity of CPU architecture porting. It primarily focuses on RISC-V architecture porting. In fact, the tool may have an average estimate of various architecture porting efforts.My focus is on the overall workload and difficulty of transplantation in the past and future,even if a project has already been ported.As part of my dataset, I have collected the **qemu** project. **I would like to gather community opinions to support my assessment. I appreciate your help and response!** Based on scanning tools, the porting complexity is determined to be high, with a significant amount of code related to the CPU architecture in the project.

You should be careful here to distinguish the code in QEMU
which is related to handling RISC-V as a *guest* architecture
(i.e. one which QEMU emulates) from the code which is related
to handling RISC-V as a *host* architecture. For purposes of
"porting QEMU to a RISC-V host", only the latter complexity counts.
The former we would have to do anyway, even if QEMU only ever
ran on x86-64 machines. You should check whether your scanner
has correctly figured this out.

-- PMM


      parent reply	other threads:[~2024-02-15 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_29796A8EF3E655396E27566AC5CE1103A509@qq.com>
2024-02-15  3:33 ` Assessment of the difficulty in porting CPU architecture for qemu Alistair Francis
2024-02-15 10:37 ` Peter Maydell [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=CAFEAcA8grC+Mi9LcNPPXqJUCVNp1a6PcEWX0nUDsOe14ARgwbw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=1584389042@qq.com \
    --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).