From: Anthony Liguori <anthony@codemonkey.ws>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Seabios dislikes -M isapc
Date: Tue, 09 Feb 2010 18:31:03 -0600 [thread overview]
Message-ID: <4B71FE47.2050300@codemonkey.ws> (raw)
In-Reply-To: <alpine.LNX.2.00.1002100325070.18215@linmac>
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
next prev parent reply other threads:[~2010-02-10 0:31 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
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 [this message]
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=4B71FE47.2050300@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=av1474@comtv.ru \
--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).