From: Paul Brook <paul@codesourcery.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa).
Date: Sat, 26 Apr 2008 22:29:02 +0100 [thread overview]
Message-ID: <200804262229.03035.paul@codesourcery.com> (raw)
In-Reply-To: <48139A27.2030601@codemonkey.ws>
> > If you configure two devices with the same IO port I'd expect writes to
> > go to one or both of them, or cause a CPU fault. Just like when you have
> > overlapping memory ranges. The device doesn't suddenly disappear in a
> > puff of smoke because the OS assigned overlapping IO ranges.
>
> The issue isn't the guest OS assigning overlapping IO regions. The
> issues is that some devices (like IDE), register ioports directly
> independently of PCI regions.
This is a device bug. They shouldn't do that. This is exactly the "manual
configuring of IO regions" you mentioned.
Paul
next prev parent reply other threads:[~2008-04-26 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 16:04 [Qemu-devel] [4261] Errors while registering ioports are not fatal (Glauber Costa) Andrzej Zaborowski
2008-04-26 19:26 ` Paul Brook
2008-04-26 19:36 ` Anthony Liguori
2008-04-26 19:57 ` Paul Brook
2008-04-26 20:33 ` Anthony Liguori
2008-04-26 20:45 ` Glauber Costa
2008-04-26 19:57 ` andrzej zaborowski
2008-04-26 20:08 ` Paul Brook
2008-04-26 20:38 ` Anthony Liguori
2008-04-26 20:54 ` Paul Brook
2008-04-26 21:09 ` Anthony Liguori
2008-04-26 21:29 ` Paul Brook [this message]
2008-04-26 20:39 ` Glauber Costa
2008-04-26 20:43 ` Anthony Liguori
2008-04-26 21:18 ` andrzej zaborowski
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=200804262229.03035.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.