All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang S <gang.chen@sunrus.com.cn>
To: "Chris Metcalf" <cmetcalf@ezchip.com>,
	"Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"walt@tilera.com" <walt@tilera.com>,
	Riku Voipio <riku.voipio@iki.fi>,
	qemu-devel <qemu-devel@nongnu.org>,
	"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/6 v4] target-tilegx: Firstly add to qemu with minimized features
Date: Sat, 28 Feb 2015 10:10:15 +0800	[thread overview]
Message-ID: <54F12387.9080205@sunrus.com.cn> (raw)
In-Reply-To: <54F0E67B.5080409@ezchip.com>

On 2/28/15 05:49, Chris Metcalf wrote:
> On 2/27/2015 12:36 PM, Andreas Färber wrote:
>> "TILE-Gx" according to
>> http://www.tilera.com/products/?ezchip=585&spage=614  - please fix
>> wherever used in textual form.
> 
> Yes, really only "tilegx" or "TILE-Gx" should be used.  In type names I agree that TileGX is probably clearer than any alternatives.
> 

OK, thanks. I shall use TILE-Gx for it.

And next, for the type names, I shall use TileGX.

>> What about CPU models? Do the Gx72, Gx36, etc. differ only in core count
>> or also in instruction set features?
> 
> From a userspace perspective, it's mostly the core count.  They also have a different set of on-chip hardware accelerators, etc., but that's out of scope for this project.
> 

OK, thanks. I guess your meaning is "For qemu, we needn't consider about
Gx72, Gx36 ..., we can treat all of them as TILE-Gx".

By the way, does Gx8000 mean 8000 core count?

Thanks.
-- 
Chen Gang

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

  reply	other threads:[~2015-02-28  2:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 13:31 [Qemu-devel] [PATCH 0/6 v4] tilegx: Can load elf64 tilegx binary successfully for linux-user Chen Gang S
2015-02-22 13:33 ` [Qemu-devel] [PATCH 1/6 v4] target-tilegx: Firstly add to qemu with minimized features Chen Gang S
2015-02-27 17:36   ` Andreas Färber
2015-02-27 21:49     ` Chris Metcalf
2015-02-28  2:10       ` Chen Gang S [this message]
2015-02-28  2:09         ` Chris Metcalf
2015-02-28  4:39           ` Chen Gang S
2015-02-28  5:20     ` Chen Gang S
2015-02-28 20:04       ` Chen Gang S
2015-02-28 19:19     ` Chen Gang S
2015-02-22 13:35 ` [Qemu-devel] [PATCH 3/6 v4] linux-user: tilegx: Add target features support within qemu Chen Gang S
2015-02-22 13:36 ` [Qemu-devel] [PATCH 4/6 v4] linux-user: Support tilegx architecture in syscall Chen Gang S
2015-02-27 17:40   ` Andreas Färber
2015-02-27 23:10     ` Chen Gang S
2015-02-22 13:36 ` [Qemu-devel] [PATCH 5/6 v4] linux-user: Support tilegx architecture in linux-user Chen Gang S
2015-02-22 13:37 ` [Qemu-devel] [PATCH 6/6 v4] linux-user/syscall.c: Switch all macros which are not defined in tilegx Chen Gang S
2015-02-27 18:24   ` Andreas Färber
2015-02-27 23:06     ` Chen Gang S
2015-02-22 18:29 ` [Qemu-devel] [PATCH 0/6 v4] tilegx: Can load elf64 tilegx binary successfully for linux-user Richard Henderson
2015-02-23  1:40   ` Chen Gang S
2015-02-22 22:32 ` Bastian Koppelmann
2015-02-23  1:37   ` Chen Gang S
2015-02-26 23:56   ` Chen Gang S
2015-02-27  0:32     ` Chen Gang S

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=54F12387.9080205@sunrus.com.cn \
    --to=gang.chen@sunrus.com.cn \
    --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.