All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <xili_gchen_5257@hotmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
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: Sun, 22 Mar 2015 06:57:03 +0800	[thread overview]
Message-ID: <BLU436-SMTP511CEF40D9A60A2D7E6BABB90F0@phx.gbl> (raw)
In-Reply-To: <CAFEAcA-_oBKMCeDRBq3QwZyn2PCp3r6BTjEfSKD9oS-Z17+ZTw@mail.gmail.com>

On 3/22/15 01:33, Peter Maydell wrote:
> 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.)
> 

OK, thanks (at present, opcode_tilegx.h has no any changes, it is only a
copy from Linux kernel).

>> 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.
> 

OK, thanks. But I have sent patches v8, please help check them, if they
are really not suitable (about splitting patch), please let me know.


> Remember to make sure that everything still compiles at every
> step in the patch series.
> 

For translate.c, it has three patches, each patch can pass compiling
(but the other patches in patch v8 can not). Please help check patches
v8 for more details, if they are really not suitable, please let me know.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2015-03-21 22:57 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
2015-03-21 22:57             ` Chen Gang [this message]
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=BLU436-SMTP511CEF40D9A60A2D7E6BABB90F0@phx.gbl \
    --to=xili_gchen_5257@hotmail.com \
    --cc=afaerber@suse.de \
    --cc=cmetcalf@ezchip.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=rth@twiddle.net \
    --cc=walt@tilera.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.