From: Richard Henderson <rth@twiddle.net>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
gxt@mprc.pku.edu.cn, qemu-devel@nongnu.org,
Claudio Fontana <claudio.fontana@gmail.com>,
proljc@gmail.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Disassembly with external objdump
Date: Sat, 10 Aug 2013 09:47:49 -1000 [thread overview]
Message-ID: <520698E5.4080409@twiddle.net> (raw)
In-Reply-To: <CAMo8BfJw9VGzb89cMYMekTusjr7zLEipuWrEUOny3rVjZsYAtg@mail.gmail.com>
On 08/10/2013 06:53 AM, Max Filippov wrote:
> On Sat, Aug 10, 2013 at 8:42 PM, Richard Henderson <rth@twiddle.net> wrote:
>> On 08/10/2013 05:45 AM, Peter Maydell wrote:
>>> Well, it depends. If we're going to dump all the in-tree
>>> disassemblers and always use an external objdump, that's fine.
>>
>> It's tempting, given that the only internal disassemblers that
>> are not missing opcodes are for the extinct cpus.
>
> Will that leave those CPUs without x/i support from monitor?
Yes.
One could always have qemu fork to objdump too. Though finding the
right one could be tricky without help.
> Does anybody use it?
That I can't answer.
r~
next prev parent reply other threads:[~2013-08-10 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 19:19 [Qemu-devel] [PATCH 0/2] Disassembly with external objdump Richard Henderson
2013-08-09 19:19 ` [Qemu-devel] [PATCH 1/2] disas: Implement fallback to dump object code as hex Richard Henderson
2013-08-09 19:19 ` [Qemu-devel] [PATCH 2/2] disas: Add disas-objdump.pl Richard Henderson
2013-08-10 4:08 ` Max Filippov
2013-08-10 10:39 ` Richard Henderson
2013-08-10 1:54 ` [Qemu-devel] [PATCH 0/2] Disassembly with external objdump Jia Liu
2013-08-10 9:16 ` Peter Maydell
2013-08-10 10:22 ` Claudio Fontana
2013-08-10 15:45 ` Peter Maydell
2013-08-10 16:42 ` Richard Henderson
2013-08-10 16:53 ` Max Filippov
2013-08-10 19:47 ` Richard Henderson [this message]
2013-09-03 13:18 ` Claudio Fontana
2013-08-11 8:59 ` Blue Swirl
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=520698E5.4080409@twiddle.net \
--to=rth@twiddle.net \
--cc=claudio.fontana@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=jcmvbkbc@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=proljc@gmail.com \
--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 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.