From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Chris Metcalf <cmetcalf@ezchip.com>
Cc: rdunlap@infradead.org, rickard_strandqvist@spectrumdigital.se,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch: tile: gxio: Export symbols for module using in 'mpipe.c'
Date: Thu, 13 Nov 2014 10:47:29 +0800 [thread overview]
Message-ID: <54641BC1.3050008@gmail.com> (raw)
In-Reply-To: <5463C07E.7070505@ezchip.com>
On 11/13/14 4:18, Chris Metcalf wrote:
> On 11/11/2014 7:16 PM, Chen Gang wrote:
>> And I also want to consult, can tile be run under qemu or other
>> simulators? Welcome any ideas, suggestions, and completions.
>
> Our use of qemu so far as been purely in the context of virtualization,
> where it functions as the KVM driver. No one has looked into using qemu
> as an instruction simulator, for example. Patches welcome :-)
>
OK, thank you for your information. And excuse me, at present, I have
no enough time resources (maybe neither have ability) for constructing
tile qemu instruction simulator.
> We do have a simulator, but for the time being, it's only available
> as part of chip sales to our customers.
>
OK, thanks. Next, I shall consult toolchains tile members for it to try
to find another ways for virtual environments (e.g. binutils/sim,
although I can not find tile under binutils/sim).
If I really can not find any virtual environments for tile, I have to
only try to test tile toolchains (gcc/binutils/libc) under full
cross-building environments, and skip tests under virtual environments.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-11-13 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 0:16 [PATCH] arch: tile: gxio: Export symbols for module using in 'mpipe.c' Chen Gang
2014-11-12 20:18 ` Chris Metcalf
2014-11-13 2:47 ` Chen Gang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-09 10:32 Chen Gang
2014-11-11 20:42 ` Chris Metcalf
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=54641BC1.3050008@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=cmetcalf@ezchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rickard_strandqvist@spectrumdigital.se \
/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