From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Chris Metcalf <cmetcalf@ezchip.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "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/5] target-tile: Firstly add to qemu with minimized features
Date: Tue, 17 Feb 2015 07:40:15 +0800 [thread overview]
Message-ID: <54E27FDF.70904@sunrus.com.cn> (raw)
In-Reply-To: <54E205F3.5050403@ezchip.com>
On 2/16/15 23:00, Chris Metcalf wrote:
> On 2/16/2015 9:44 AM, Chen Gang S wrote:
>> Excuse me, after comparing the code details between kernel version
>> disassembler and binutils version disassembler, I am sure the kernel
>> version disassembler is the part of the binutils version disassembler:
>
> Yes, exactly. We used an unifdef tool and some reindenting to generate the
> kernel version from the same master that we used to generate the binutils
> version. We released the two under different licenses. I'm pretty comfortable
> that all of this is in the letter and spirit of copyright and license.
>
> So you can start with the kernel version and you will inherit the GPL v2 license
> of that code.
>
OK, thanks, so I can continue. :-)
>> - kernel version decode_X1_fsm[1206] is older than binutils version
>> decode_X1_fsm[1266].
>
> I'm pretty sure this represents the ld_tls family of instructions that are present
> in binutils. However, these are updated by the runtime loader, so you won't see
> them if you are disassembling live code anyway. If it for some reason this becomes
> an issue, I expect we could generate an appropriate update for the kernel version.
>
OK, thanks. At present, I just skip them, if I really meet the related
issue (I guess not), I shall notify to tile related members.
>> I guess, for qemu, we need !DISASM_ONLY, and may need BFD_RELOC, and may
>> need the latest decode_X1_fsm, and also may need !__KERNEL__ -- which
>> means we will use the full binutils version disassembler!!
>>
>> In current condition, I really don't know how to do next. Welcome any
>> ideas, and suggestions.
>
> Honestly, I'm not sure that that's true. Mostly you just need to be able to
> recognize instructions, I would think. I suspect it's worth pushing ahead with
> the kernel stuff as a base and see more precisely what you think is missing.
> I don't know the qemu requirements well enough to give an educated opinion.
>
OK, thanks.
> The disassembly stuff in the kernel allows you to recognize instructions, extract
> operands (registers and immediates), etc.
>
OK, thanks, I guess, you mean that we can still be DISASM_ONLY (if what
I guess is incorrect, please let me know).
> There is also some code in glibc's sysdep/tile/dl-machine.h which implements the
> runtime loader relocation processing, under GPL v2.1; perhaps some of that would
> be relevant to what qemu does? Again, I'm not really sure.
>
OK, thanks, I guess you mean we need consider about BFD_RELOC, and may
reference glib implementation to get help (binutils implements BFD_RELOC
with the almost simplest and fewest code, but we can not use them).
And I shall also try "!__KERNEL__ && !__LIBC__" to see the result, then
decide whether we use them or not (I guess we can skip them, just like
kernel version disassembler has done).
Thanks
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-02-16 23:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:14 [Qemu-devel] [PATCH 0/5] tile: Can load elf64 tilegx binary successfully for linux-user Chen Gang S
2015-02-12 21:15 ` [Qemu-devel] [PATCH 1/5] target-tile: Firstly add to qemu with minimized features Chen Gang S
2015-02-13 23:50 ` Chen Gang S
2015-02-14 0:26 ` Peter Maydell
2015-02-14 2:40 ` Richard Henderson
2015-02-14 3:14 ` Chen Gang S
2015-02-14 3:08 ` Chen Gang S
2015-02-14 3:08 ` Peter Maydell
2015-02-14 3:37 ` Chris Metcalf
2015-02-14 5:47 ` Peter Maydell
2015-02-14 15:53 ` Chen Gang S
2015-02-16 3:40 ` Chen Gang S
2015-02-16 14:44 ` Chen Gang S
2015-02-16 15:00 ` Chris Metcalf
2015-02-16 23:40 ` Chen Gang S [this message]
2015-02-16 15:24 ` Max Filippov
2015-02-16 23:08 ` Chen Gang S
2015-02-16 23:46 ` Peter Maydell
2015-02-17 0:11 ` Chris Metcalf
2015-02-17 2:48 ` Chen Gang S
2015-02-17 3:11 ` Chen Gang S
2015-02-17 3:18 ` Chen Gang S
2015-02-17 0:29 ` Chris Metcalf
2015-02-17 2:03 ` Chen Gang S
2015-04-27 21:12 ` [Qemu-devel] [Consult] About SPRs information Chen Gang
2015-04-27 22:04 ` Richard Henderson
2015-04-28 20:19 ` Chen Gang
2015-04-28 21:32 ` Chen Gang
2015-04-28 21:43 ` Peter Maydell
2015-04-29 13:32 ` Chen Gang
2015-05-02 2:42 ` Chen Gang
2015-05-02 4:09 ` Chen Gang
2015-05-03 14:30 ` Chen Gang
2015-05-07 21:05 ` Chen Gang
2015-05-08 3:14 ` Peter Maydell
2015-05-08 23:18 ` Chen Gang
2015-02-14 15:43 ` [Qemu-devel] [PATCH 1/5] target-tile: Firstly add to qemu with minimized features Chen Gang S
2015-02-12 21:17 ` [Qemu-devel] [PATCH 3/5] linux-user: tile: Add target features support within qemu Chen Gang S
2015-02-12 21:18 ` [Qemu-devel] [PATCH 4/5] linux-user: Support tile architecture in syscall Chen Gang S
2015-02-12 21:20 ` [Qemu-devel] [PATCH 5/5] linux-user: Support tile architecture in linux-user 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=54E27FDF.70904@sunrus.com.cn \
--to=gang.chen@sunrus.com.cn \
--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.