qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Justen <jljusten@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Implement PC port80 debug register.
Date: Mon, 29 Jun 2009 08:26:41 -0700	[thread overview]
Message-ID: <2a50f7880906290826t4128b11dyc68a36fd01e8208c@mail.gmail.com> (raw)
In-Reply-To: <4A48CE67.9070705@redhat.com>

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

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.

-Jordan

On Mon, Jun 29, 2009 at 7:23 AM, Avi Kivity <avi@redhat.com> wrote:

> On 06/29/2009 04:47 PM, Anthony Liguori wrote:
>
>> Jordan Justen wrote:
>>
>>> From: jljusten <jljusten@jljusten-laptop.(none)>
>>>
>>> In PC systems, the byte I/O port 0x80 is commonly made into a
>>> read/write byte.  BIOS and/or system software will often use
>>> it as a simple checkpoint marker.
>>>
>>
>> What software does this?  Typically, port80 is used as an IO delay
>> mechanism.  I'm not aware of it being used to read/write arbitrary data.
>>
>>
> It's often used in BIOS code.  There used to be seven-segment cards you'd
> plug into a computer that would show you port 80 in real time.  I think it's
> a write-only port, though.
>
> --
> error compiling committee.c: too many arguments to function
>
>

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

  parent reply	other threads:[~2009-06-29 15:26 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 [this message]
2009-06-29 15:31       ` Anthony Liguori
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=2a50f7880906290826t4128b11dyc68a36fd01e8208c@mail.gmail.com \
    --to=jljusten@gmail.com \
    --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).