From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Jinsong Liu <jinsong.liu@intel.com>,
qemu-devel <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [PATCH v2 0/7] APIC/IOAPIC cleanup
Date: Mon, 23 Aug 2010 13:25:44 +0300 [thread overview]
Message-ID: <4C724CA8.5080102@redhat.com> (raw)
In-Reply-To: <74BFF8A5-7CB6-40F8-A9D0-5E5E6368C5EE@suse.de>
On 08/23/2010 01:18 PM, Alexander Graf wrote:
>
>> I certainly don't, but others may.
>>
>> However, the problem remains: every time real hardware doesn't fit our pretty model we'll drop support for that hardware?
> No, every time real hardware doesn't fit out pretty model and nobody really cares, we don't care.
>
> Seriously - would you want to start off modeling everything so that EISA and MCA fit in too?
Look how this developed:
1. apic.c has an incestuous relationship with the cpu
2. let's make them one and the same
3. but in real life they're not one and the same in some cases
4. including some we support
5. let's drop support for those
vs
1. hardware isn't a tree
2. we have to live with that
Dropping support for 486 is fine, but let's not do it because we want to
model hardware in a way that's different from reality
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-23 10:26 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 21:14 [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup Blue Swirl
2010-06-13 16:56 ` [Qemu-devel] " Jan Kiszka
2010-06-13 17:03 ` Andreas Färber
2010-06-13 17:53 ` Blue Swirl
2010-06-13 18:17 ` Andreas Färber
2010-06-13 17:49 ` Blue Swirl
2010-08-19 19:33 ` [Qemu-devel] " Anthony Liguori
2010-08-19 20:09 ` Blue Swirl
2010-08-19 20:49 ` Anthony Liguori
2010-08-19 21:21 ` Blue Swirl
2010-08-19 21:51 ` Anthony Liguori
2010-08-19 22:52 ` malc
2010-08-20 1:01 ` Anthony Liguori
2010-08-20 10:00 ` malc
2010-08-20 8:42 ` [Qemu-devel] " Paolo Bonzini
2010-08-20 17:01 ` [Qemu-devel] " Markus Armbruster
2010-08-20 18:38 ` Anthony Liguori
2010-08-22 20:28 ` Avi Kivity
2010-08-22 21:02 ` Anthony Liguori
2010-08-23 5:46 ` Avi Kivity
2010-08-23 13:23 ` Anthony Liguori
2010-08-23 13:42 ` Avi Kivity
2010-08-23 13:48 ` Anthony Liguori
2010-08-23 14:00 ` Avi Kivity
2010-08-23 14:26 ` Anthony Liguori
2010-08-23 14:32 ` Avi Kivity
2010-08-23 14:47 ` Anthony Liguori
2010-08-23 15:10 ` Markus Armbruster
2010-08-23 16:05 ` Anthony Liguori
2010-08-23 17:36 ` Markus Armbruster
2010-08-23 17:47 ` Anthony Liguori
2010-08-23 18:24 ` [Qemu-devel] " Jan Kiszka
2010-08-23 18:29 ` Anthony Liguori
2010-08-23 15:14 ` [Qemu-devel] " Avi Kivity
2010-08-23 16:02 ` Anthony Liguori
2010-08-24 9:51 ` Avi Kivity
2010-08-20 19:26 ` Blue Swirl
2010-08-20 10:35 ` [Qemu-devel] " Jan Kiszka
2010-08-22 9:37 ` [Qemu-devel] " Avi Kivity
2010-08-22 18:52 ` Anthony Liguori
2010-08-22 19:44 ` Avi Kivity
2010-08-22 20:03 ` Anthony Liguori
2010-08-22 20:33 ` Avi Kivity
2010-08-22 21:06 ` Anthony Liguori
2010-08-23 5:49 ` Avi Kivity
2010-08-23 9:09 ` [Qemu-devel] " Jan Kiszka
2010-08-23 9:25 ` Avi Kivity
2010-08-23 10:11 ` Alexander Graf
2010-08-23 10:15 ` Avi Kivity
2010-08-23 10:18 ` Alexander Graf
2010-08-23 10:25 ` Avi Kivity [this message]
2010-08-22 21:07 ` [Qemu-devel] " Anthony Liguori
2010-08-23 5:48 ` Avi Kivity
2010-08-22 9:13 ` Avi Kivity
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=4C724CA8.5080102@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=jinsong.liu@intel.com \
--cc=paul@codesourcery.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).