qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Justen <jljusten@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
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 09:07:28 -0700	[thread overview]
Message-ID: <2a50f7880906290907m60bda19cy53a58c97fd014c73@mail.gmail.com> (raw)
In-Reply-To: <4A48DE4A.7090706@codemonkey.ws>

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

Anthony,

That seems like a reasonable request.

So, a 'info port80' command would be preferable to having i/o port 0x80 be
read/write?

I still think the read/write port route would
* better emulate systems,
* be more flexible (allowing software the option to read it),
* and, be easier to implement :)

But, I think the most important part is to make the data accessible
somehow.  So, the monitor access method would work fine as well.

-Jordan

On Mon, Jun 29, 2009 at 8:31 AM, Anthony Liguori <anthony@codemonkey.ws>wrote:

> 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
>
>

[-- Attachment #2: Type: text/html, Size: 1706 bytes --]

  reply	other threads:[~2009-06-29 16:07 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
2009-06-29 16:07         ` Jordan Justen [this message]
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=2a50f7880906290907m60bda19cy53a58c97fd014c73@mail.gmail.com \
    --to=jljusten@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.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).