From: Anthony Liguori <anthony@codemonkey.ws>
To: Natalia Portillo <claunia@claunia.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Seabios dislikes -M isapc
Date: Tue, 09 Feb 2010 15:05:16 -0600 [thread overview]
Message-ID: <4B71CE0C.90204@codemonkey.ws> (raw)
In-Reply-To: <24DBE33F-1742-4534-A943-65D9A3579A81@claunia.com>
On 02/09/2010 02:36 PM, Natalia Portillo wrote:
> There are operating systems that simple conflict with some assumptions
> made by PCI architecture.
>
> Rembember that the PC memory map changed to include the PCI
> configuration space and so on, space that can be expected to contain
> other data, or not at all, and could be used in ISA/EISA/VLB/MCA
> systems by PCI-unaware operating systems or applications.
But practically speaking, given the devices that we emulate, is there
any workload that works with -M isapc but not -M pc?
Having to support an ISA and PCI system in the BIOS is a bit of a
burden. If we can eliminate that without regressing any guest
workloads, I think it would be a net win.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-02-09 21:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 10:17 [Qemu-devel] Seabios dislikes -M isapc Jan Kiszka
2010-02-08 18:38 ` [Qemu-devel] " Sebastian Herbszt
2010-02-08 19:09 ` Jan Kiszka
2010-02-09 0:51 ` Kevin O'Connor
2010-02-09 20:47 ` Sebastian Herbszt
2010-02-09 19:45 ` [Qemu-devel] " Andreas Färber
2010-02-09 19:50 ` Anthony Liguori
2010-02-09 20:36 ` Natalia Portillo
2010-02-09 21:05 ` Anthony Liguori [this message]
2010-02-09 21:36 ` Natalia Portillo
2010-02-09 21:41 ` Anthony Liguori
2010-02-09 22:41 ` malc
2010-02-09 23:25 ` Aurelien Jarno
2010-02-09 23:28 ` malc
2010-02-10 0:00 ` Anthony Liguori
2010-02-10 0:27 ` malc
2010-02-10 0:31 ` Anthony Liguori
2010-02-11 23:51 ` Jamie Lokier
2010-02-12 2:44 ` Anthony Liguori
2010-02-09 23:27 ` Natalia Portillo
2010-02-09 23:30 ` malc
2010-02-09 22:37 ` malc
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=4B71CE0C.90204@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=claunia@claunia.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).