From: =?gb18030?B?eGlhb2xlaQ==?= <1482995675@qq.com>
To: =?gb18030?B?QWxleCBCZW5uqKZl?= <alex.bennee@linaro.org>,
=?gb18030?B?cWVtdS1kZXZlbA==?= <qemu-devel@nongnu.org>
Subject: =?gb18030?B?u9i4tKO6IEdEQiBnZXQgd3JvbmcgZGVidWcgaW5mb3Mgb24gVEkgRFNQIGFyY2hpdGVjdHVyZSBleHRlbnNpb24=?=
Date: Thu, 28 May 2020 17:49:19 +0800 [thread overview]
Message-ID: <tencent_1EBC79D30BA701D4EC6F31B2442DFE3E5C08@qq.com> (raw)
In-Reply-To: <87v9kg4fw4.fsf@linaro.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1767 bytes --]
Hi ,
Thanks for the hint.
I have been looking for how QEMU determine the target program terminates by checking the host implementation (eg i386). I thought the target program termination is connected to the initial FP pushed to stack, I am not sure this is how QEMU does. Could you be more specific on the termination check ? is it target architecture dependent( an added DSP target architecture should deal with it explicitly)?
Thanks again
xiaolei
------------------ ÔʼÓʼþ ------------------
·¢¼þÈË: "Alex Benn¨¦e"<alex.bennee@linaro.org>;
·¢ËÍʱ¼ä: 2020Äê5ÔÂ28ÈÕ(ÐÇÆÚËÄ) ÏÂÎç4:34
ÊÕ¼þÈË: "casmac"<1482995675@qq.com>;
³ËÍ: "Philippe Mathieu-Daud¨¦"<f4bug@amsat.org>;"qemu-devel"<qemu-devel@nongnu.org>;
Ö÷Ìâ: Re: GDB get wrong debug infos on TI DSP architecture extension
casmac <1482995675@qq.com> writes:
> Hi,
Thank you for forwarding my question to developers and sharing the C6x implementation.
> Perhaps I should follow up with another problem I encountered. The senerio is the emulator keeps running eventhough the program it emulates has already exited. And it keeps retrieving instructions which are all zero "instruction"(0x00000000).
>
> It looks to me that in function cpu_exec(CPUState *cpu), the following loop never terminate:
> while (!cpu_handle_exception(cpu, &ret)) {
> TranslationBlock *last_tb = NULL;
> int tb_exit = 0;
> while (!cpu_handle_interrupt(cpu, &last_tb)) { ... }
> Is it because cpu->exit_request remains 0 ?
>
> At what point should we make cpu->exit_request=1 ?
cpu->exit_request is set for asynchronus conditions (e.g. timer IRQs or
IO events). A number of helpers will "kick" the cpu by calling
cpu_exit().
> Thanks again!!
>
>
> regards
> xiaolei
>
>
>
next prev parent reply other threads:[~2020-05-28 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 6:48 GDB get wrong debug infos on TI DSP architecture extension casmac
2020-05-27 7:19 ` Philippe Mathieu-Daudé
2020-05-27 21:41 ` Taylor Simpson
2020-05-29 7:27 ` casmac
2020-05-29 15:19 ` Taylor Simpson
2020-05-28 1:16 ` casmac
2020-05-28 8:34 ` Alex Bennée
2020-05-28 9:49 ` =?gb18030?B?eGlhb2xlaQ==?= [this message]
2020-05-27 9:11 ` Alex Bennée
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=tencent_1EBC79D30BA701D4EC6F31B2442DFE3E5C08@qq.com \
--to=1482995675@qq.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).