From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
Taylor Simpson <tsimpson@quicinc.com>
Cc: "Alessandro Di Federico" <ale@rev.ng>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Niccolò Izzo" <izzoniccolo@gmail.com>,
"nizzo@rev.ng" <nizzo@rev.ng>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Aleksandar Markovic" <aleksandar.m.mail@gmail.com>
Subject: Re: QEMU for Qualcomm Hexagon - KVM Forum talk and code available
Date: Wed, 18 Dec 2019 13:50:15 -1000 [thread overview]
Message-ID: <ba5ef3ee-aafe-0770-10c8-4a020cc423e9@linaro.org> (raw)
In-Reply-To: <CAFEAcA-TpZfqbWjGX-tD0Osapt_K4yuTBg6+B=ZxU4MuVr7omg@mail.gmail.com>
On 12/17/19 8:21 AM, Peter Maydell wrote:
> On Tue, 17 Dec 2019 at 18:16, Taylor Simpson <tsimpson@quicinc.com> wrote:
>> Question 2:
>> What is the best source of guidance on breaking down support for a new target into a patch series?
>
> Look at how previous ports did it.
E.g. the hppa-linux-user port. The initial merge ends at ebe9383caefd.
There are 15 patches -- mostly in linux-user -- before the one that enables
compilation. At which point exactly zero instructions are actually implemented.
The actual cpu emulation comes afterwards in 8 patches (hppa 1.1 isn't terribly
complicated).
r~
next prev parent reply other threads:[~2019-12-18 23:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 16:26 QEMU for Qualcomm Hexagon - KVM Forum talk and code available Taylor Simpson
2019-11-01 18:29 ` Philippe Mathieu-Daudé
2019-11-04 2:35 ` Taylor Simpson
2019-11-05 0:05 ` Aleksandar Markovic
2019-11-05 16:32 ` Taylor Simpson
2019-11-12 22:52 ` Taylor Simpson
2019-11-13 10:31 ` Alex Bennée
2019-11-13 19:31 ` Taylor Simpson
2019-11-13 21:10 ` Richard Henderson
2019-11-15 0:54 ` Taylor Simpson
2019-12-17 18:14 ` Taylor Simpson
2019-12-17 18:19 ` Thomas Huth
2019-12-17 18:21 ` Peter Maydell
2019-12-17 18:41 ` Philippe Mathieu-Daudé
2019-12-17 18:44 ` Philippe Mathieu-Daudé
2019-12-18 23:50 ` Richard Henderson [this message]
2019-11-13 21:27 ` Peter Maydell
2019-11-19 9:12 ` Philippe Mathieu-Daudé
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=ba5ef3ee-aafe-0770-10c8-4a020cc423e9@linaro.org \
--to=richard.henderson@linaro.org \
--cc=ale@rev.ng \
--cc=aleksandar.m.mail@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=izzoniccolo@gmail.com \
--cc=nizzo@rev.ng \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.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).