From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NexGq-00070j-J0
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 16:05:20 -0500
Received: from [199.232.76.173] (port=33833 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NexGq-00070B-31
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 16:05:20 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <anthony@codemonkey.ws>) id 1NexGo-0005tV-Ro
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 16:05:19 -0500
Received: from mail-yx0-f183.google.com ([209.85.210.183]:50840)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NexGo-0005tP-JN
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 16:05:18 -0500
Received: by yxe13 with SMTP id 13so113592yxe.18
	for <qemu-devel@nongnu.org>; Tue, 09 Feb 2010 13:05:18 -0800 (PST)
Message-ID: <4B71CE0C.90204@codemonkey.ws>
Date: Tue, 09 Feb 2010 15:05:16 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Seabios dislikes -M isapc
References: <4B6FE4BD.5010304@siemens.com> <4B71BC80.30905@codemonkey.ws>
	<24DBE33F-1742-4534-A943-65D9A3579A81@claunia.com>
In-Reply-To: <24DBE33F-1742-4534-A943-65D9A3579A81@claunia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Natalia Portillo <claunia@claunia.com>
Cc: qemu-devel@nongnu.org

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