From: Richard Henderson <richard.henderson@linaro.org>
To: Lucien Murray-Pitts <lucienmp.qemu@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Lucien Anti-Spam <lucienmp_antispam@yahoo.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] RFC: Why does target/m68k RTE insn. use gen_exception
Date: Tue, 9 Jul 2019 21:04:15 +0200 [thread overview]
Message-ID: <d9e5602c-bb33-1812-ebc2-b533e9dd5f25@linaro.org> (raw)
In-Reply-To: <CALvKS=GvAkNr3OKZzjGoTGG_Eys76zjcjodiN4hKXjFM5B0a4A@mail.gmail.com>
On 7/9/19 6:58 PM, Lucien Murray-Pitts wrote:
> Any suggestions on how to obtain pc_next from the "m68k_cpu_do_interrupt(
> CPUState *cs)" ?
I did have a suggestion. It was fairly detailed.
https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg06522.html
r~
next prev parent reply other threads:[~2019-07-09 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2136180936.260219.1561641583358.ref@mail.yahoo.com>
2019-06-27 13:19 ` [Qemu-devel] RFC: Why does target/m68k RTE insn. use gen_exception Lucien Anti-Spam via Qemu-devel
2019-06-27 13:22 ` Lucien Anti-Spam via Qemu-devel
2019-06-27 17:09 ` Richard Henderson
2019-06-28 0:27 ` Lucien Murray-Pitts
2019-06-28 9:35 ` Richard Henderson
2019-06-28 15:50 ` Lucien Murray-Pitts
2019-06-29 10:15 ` Richard Henderson
2019-06-29 16:36 ` Lucien Murray-Pitts
2019-06-30 8:20 ` Richard Henderson
2019-07-01 9:10 ` Peter Maydell
2019-07-01 12:04 ` Lucien Anti-Spam via Qemu-devel
2019-07-01 12:11 ` Peter Maydell
2019-07-09 16:58 ` Lucien Murray-Pitts
2019-07-09 17:06 ` Peter Maydell
2019-07-09 19:04 ` Richard Henderson [this message]
2019-07-10 13:35 ` Lucien Murray-Pitts
2019-07-10 17:50 ` Lucien Murray-Pitts
2019-07-10 18:15 ` Alex Bennée
2019-07-11 9:00 ` Peter Maydell
2019-07-11 9:18 ` Richard Henderson
2019-07-12 20:55 ` Lucien Murray-Pitts
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=d9e5602c-bb33-1812-ebc2-b533e9dd5f25@linaro.org \
--to=richard.henderson@linaro.org \
--cc=laurent@vivier.eu \
--cc=lucienmp.qemu@gmail.com \
--cc=lucienmp_antispam@yahoo.com \
--cc=peter.maydell@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).