From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] mini documentation of "info registers" output
Date: Fri, 1 Jul 2005 11:33:49 +0700 [thread overview]
Message-ID: <200507011133.49905.a_mulyadi@softhome.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
Dear list
Here is a little cheat sheet for you to better understand what "info
registers" shows on qemu's monitor. This infomations are strictly for
x86
Feel free to correct or send feedbacks about this document
PS: Hetz, please "copy" this document toward Qemu forums.... Thank you
in advance...
regards
Mulyadi
[-- Attachment #2: info-registers-mini-document-English.zip --]
[-- Type: application/x-zip, Size: 1416 bytes --]
next reply other threads:[~2005-07-01 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 4:33 Mulyadi Santosa [this message]
2005-07-01 12:17 ` [Qemu-devel] mini documentation of "info registers" output Paul Brook
2005-07-02 4:12 ` Mulyadi Santosa
2005-07-02 7:18 ` Gwenole Beauchesne
2005-07-02 15:08 ` Paul Brook
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=200507011133.49905.a_mulyadi@softhome.net \
--to=a_mulyadi@softhome.net \
--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).