From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nf0U2-0000DM-Ok for qemu-devel@nongnu.org; Tue, 09 Feb 2010 19:31:10 -0500 Received: from [199.232.76.173] (port=46099 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nf0U2-0000DA-E7 for qemu-devel@nongnu.org; Tue, 09 Feb 2010 19:31:10 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nf0U1-00026u-5T for qemu-devel@nongnu.org; Tue, 09 Feb 2010 19:31:10 -0500 Received: from mail-iw0-f185.google.com ([209.85.223.185]:41953) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nf0U0-00026m-UL for qemu-devel@nongnu.org; Tue, 09 Feb 2010 19:31:09 -0500 Received: by iwn15 with SMTP id 15so6077781iwn.19 for ; Tue, 09 Feb 2010 16:31:08 -0800 (PST) Message-ID: <4B71FE47.2050300@codemonkey.ws> Date: Tue, 09 Feb 2010 18:31:03 -0600 From: Anthony Liguori 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> <4B71CE0C.90204@codemonkey.ws> <7DDDDCA5-2F86-4644-B7B3-A714AEDA56CA@claunia.com> <20100209232531.GC2462@volta.aurel32.net> <4B71F72D.8090703@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: malc Cc: qemu-devel@nongnu.org, Aurelien Jarno On 02/09/2010 06:27 PM, malc wrote: > APIC is almost as good as useless without ACPI and we have a switch to > disable that. > Which is another thing that I'm not sure it all that useful to have. >> Firmware is really hard to implement if you have to deal with supporting >> multiple chipsets. >> >> Also, if we don't have a workload that actually needs isapc, that suggests >> that there's no real way to test that isapc doesn't have non-ISA things creep >> into it. >> >> Given that, I'm inclined to suggest that we mark isapc as deprecated, give >> people some time to comment on it, and then provided that we still don't think >> it's necessary, change isapc to simply use isa devices while still using a PCI >> chipset. >> > Not to comment, to give hard evidence that something is working with isapc > and doesn't otherwise, in which case it must stay. > Yes. If someone can produce a workload that requires isapc[1], I'm all for continuing to support it. [1] Very specifically, I mean requires -M isapc to only emulate an ISA bus and not emulate an ISA bus via a bridge in the PIIX chipset. We will always need an -M isapc that only uses ISA devices instead of PCI devices. However, if we can use a PCI chipset in -M isapc, we can express the differences entirely via qdev. Regards, Anthony Liguori