From: Richard Henderson <rth@twiddle.net>
To: "Chen Gang" <xili_gchen_5257@hotmail.com>,
"Chris Metcalf" <cmetcalf@ezchip.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Andreas Färber" <afaerber@suse.de>
Cc: "walt@tilera.com" <walt@tilera.com>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 00/12 v9] tilegx: Firstly add tilegx feature for linux-user
Date: Fri, 27 Mar 2015 10:01:31 -0700 [thread overview]
Message-ID: <55158CEB.5000806@twiddle.net> (raw)
In-Reply-To: <BLU436-SMTP63FBE361847178B437A0A7B9090@phx.gbl>
On 03/27/2015 03:47 AM, Chen Gang wrote:
> After load elf64 binary, qemu tilegx can finish executing the first
> system call (uname) successfully in _dl_discover_osversion(), and
> return to __libc_start_main().
>
> Chen Gang (12):
> linux-user: tilegx: Firstly add architecture related features
> linux-user: tilegx: Add target features support within qemu
> linux-user: Support tilegx architecture in syscall
> linux-user: Support tilegx architecture in linux-user
> linux-user/syscall.c: conditionalize syscalls which are not defined in
> tilegx
> target-tilegx: Add cpu basic features for linux-user
> target-tilegx: Add helper features for linux-user
> target-tilegx: Add opcode basic implementation for tilegx
> target-tilegx: Finish processing bundle and preparing decoding pipes
> target-tilegx: Add TILE-Gx building files
> target-tilegx: Decoding pipes to support finish running 1st system
> call
> target-tilegx: Generate tcg instructions to execute to 1st system call
Reviewed-by: Richard Henderson <rth@twiddle.net>
r~
next prev parent reply other threads:[~2015-03-27 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 10:47 [Qemu-devel] [PATCH 00/12 v9] tilegx: Firstly add tilegx feature for linux-user Chen Gang
2015-03-27 17:01 ` Richard Henderson [this message]
2015-03-27 23:21 ` 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=55158CEB.5000806@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.de \
--cc=cmetcalf@ezchip.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--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 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.