From: "François Revol" <revol@free.fr>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] [RFC] PPC: dump DCRs from monitor
Date: Thu, 30 Aug 2012 12:01:22 +0200 [thread overview]
Message-ID: <503F39F2.7050908@free.fr> (raw)
In-Reply-To: <86B075B2-13F7-486F-9C48-9DDE2ECDF45B@suse.de>
On 29/08/2012 19:55, Alexander Graf wrote:
>>> Are they accessible through the monitor's p command? Would be good to implement there too if not.
>>
>> I don't think so, which syntax would you use anyway? $dcr[n] ?
>
> Sure, why not? Is that possible with the register parsing code? I don't know that one too well,
> but it's probably the best fit for you, right?
Except I don't know the parsing code well enough to not waste time
digging it...
For now the full dump is enough to me, I suppose if someone wants more
he can also send a patch ;-)
We could also add logging to the read/write calls to see the ordering.
For now I just added some printf in my code just like in ppc405*.
François.
prev parent reply other threads:[~2012-08-30 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 11:03 [Qemu-devel] [PATCH] [RFC] PPC: dump DCRs from monitor François Revol
2012-08-29 14:53 ` Alexander Graf
2012-08-29 17:43 ` François Revol
2012-08-29 17:55 ` Alexander Graf
2012-08-30 10:01 ` François Revol [this message]
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=503F39F2.7050908@free.fr \
--to=revol@free.fr \
--cc=agraf@suse.de \
--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).