From: Anthony Liguori <anthony@codemonkey.ws>
To: Jordan Justen <jljusten@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Implement PC port80 debug register.
Date: Mon, 29 Jun 2009 10:31:22 -0500 [thread overview]
Message-ID: <4A48DE4A.7090706@codemonkey.ws> (raw)
In-Reply-To: <2a50f7880906290826t4128b11dyc68a36fd01e8208c@mail.gmail.com>
Jordan Justen wrote:
> Avi,
>
> Well, I am not sure if this it globally the case for PC motherboards,
> but in my experience, it has been read/write.
>
> At least for a system such as qemu, it make it difficult to use the
> port80 checkpoint of software without being able to read the last
> value written.
It seems like the more logical thing to do is to save the port80 write
and have it obtainable via the monitor.
But really, we have other debug mechanisms for BIOSes (like ports
50x/40x). That seems like a better thing to use if you're writing
custom code for QEMU.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-29 15:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 8:05 [Qemu-devel] [PATCH] Implement PC port80 debug register Jordan Justen
2009-06-29 13:47 ` Anthony Liguori
2009-06-29 14:17 ` Paul Brook
2009-06-29 14:23 ` Avi Kivity
2009-06-29 14:34 ` Chris Lalancette
2009-06-29 15:26 ` Jordan Justen
2009-06-29 15:31 ` Anthony Liguori [this message]
2009-06-29 16:07 ` Jordan Justen
2009-06-29 17:11 ` Avi Kivity
2009-06-29 18:39 ` Anthony Liguori
2009-06-29 18:43 ` Avi Kivity
2009-06-29 18:46 ` Alexander Graf
2009-06-29 18:57 ` Avi Kivity
2009-06-29 19:00 ` Jordan Justen
2009-06-29 19:02 ` Jordan Justen
2009-07-01 7:39 ` Jordan Justen
2009-07-09 18:58 ` Anthony Liguori
2009-06-29 15:36 ` Avi Kivity
2009-06-29 21:53 ` Jamie Lokier
2009-06-29 23:18 ` Carl-Daniel Hailfinger
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=4A48DE4A.7090706@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jljusten@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 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).