From: Peter Maydell <peter.maydell@linaro.org>
To: Chen Gang <xili_gchen_5257@hotmail.com>
Cc: "Riku Voipio" <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>,
"Chris Metcalf" <cmetcalf@ezchip.com>,
"walt@tilera.com" <walt@tilera.com>,
"Andreas Färber" <afaerber@suse.de>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/6 v7] target-tilegx: Firstly add TILE-Gx with minimized features
Date: Sat, 21 Mar 2015 17:33:10 +0000 [thread overview]
Message-ID: <CAFEAcA-_oBKMCeDRBq3QwZyn2PCp3r6BTjEfSKD9oS-Z17+ZTw@mail.gmail.com> (raw)
In-Reply-To: <BLU436-SMTP1060EA8F528CFDD4E84FC39B90E0@phx.gbl>
On 20 March 2015 at 23:57, Chen Gang <xili_gchen_5257@hotmail.com> wrote:
> For 'opcode_tilegx.h', it comes from Linux kernel which is already more
> than 1000 lines. For me, I still suggest to let it within one patch.
Right, for that sort of special case you should put it in
a single patch which is just "Import copy of whatever.h from Linux
kernel", and which has nothing else in it except for the imported
file or files, and which makes no QEMU specific changes to those
files. Then people can skim through that patch quickly knowing
they don't have to look for any changes or extras that do need
review. (If there is some tweak that needs to be made for QEMU's
purposes that can go in a subsequent patch.)
> For 'translate.c', I try to split it into 3 patches:
>
> - parsing bundle and decode to the first level of pipe,
>
> - parsing 2nd level of pipe.
>
> - generate tcg code.
>
> For the left files:
>
> - 'configure', 'Makefile.obj', 'tilegx-linux-user.mak' are in a patch.
>
> - 'cpu*' are in a patch
>
> - 'help.*' are in a patch.
I would suggest that rather than having "cpu* in one patch
and help* in another" (ie a split by file), you split things
functionally, so you might have a patch adding "support for
instruction group foo" which includes everything needed
for those instructions including the translate.c changes
and the helper functions that get called by the generated
code.
Remember to make sure that everything still compiles at every
step in the patch series.
-- PMM
next prev parent reply other threads:[~2015-03-21 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <550C3B78.3050802@hotmail.com>
2015-03-20 15:25 ` [Qemu-devel] [PATCH 1/6 v7] target-tilegx: Firstly add TILE-Gx with minimized features Chen Gang
2015-03-20 17:45 ` Richard Henderson
2015-03-20 23:32 ` Chen Gang
2015-03-20 17:48 ` Peter Maydell
2015-03-20 22:52 ` Chen Gang
2015-03-20 23:30 ` Peter Maydell
2015-03-20 23:57 ` Chen Gang
2015-03-21 17:33 ` Peter Maydell [this message]
2015-03-21 22:57 ` Chen Gang
2015-03-20 15:26 ` [Qemu-devel] [PATCH 2/6 v7] linux-user: tilegx: Firstly add architecture related features Chen Gang
2015-03-20 15:26 ` [Qemu-devel] [PATCH 3/6 v7] linux-user: tilegx: Add target features support within qemu Chen Gang
2015-03-20 15:27 ` [Qemu-devel] [PATCH 4/6 v7] linux-user: Support tilegx architecture in syscall Chen Gang
2015-03-20 15:28 ` [Qemu-devel] [PATCH 5/6 v7] linux-user: Support tilegx architecture in linux-user Chen Gang
2015-03-20 15:29 ` [Qemu-devel] [PATCH 6/6 v7] linux-user/syscall.c: conditionalize syscalls which are not defined in tilegx Chen Gang
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=CAFEAcA-_oBKMCeDRBq3QwZyn2PCp3r6BTjEfSKD9oS-Z17+ZTw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=cmetcalf@ezchip.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
--cc=walt@tilera.com \
--cc=xili_gchen_5257@hotmail.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).