From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] KVM call minutes for Feb 8
Date: Thu, 10 Feb 2011 15:00:49 +0100
Message-ID: <4D53EF91.7030400@codemonkey.ws>
References: <m3r5bhhc0d.fsf@blackfin.pond.sub.org>	<4D526D0D.9020507@codemonkey.ws>	<m3pqr1s86w.fsf@blackfin.pond.sub.org>	<4D52A86A.1030407@codemonkey.ws>	<AANLkTimtswr5fN9PGVnTSxb9szu12bTC0s4tVwbku-J5@mail.gmail.com>	<4D52F20A.7070009@codemonkey.ws>	<AANLkTi=JzM21XfDR+YO9JY=e8ONGDWVR6YeYdQ7jzzrk@mail.gmail.com>	<4D539800.3070802@codemonkey.ws>	<20110210090748.GD673@redhat.com>	<4D53BD22.1040800@redhat.com>	<20110210111354.GA21681@redhat.com>	<4D53DF42.4030700@codemonkey.ws> <4D53E155.5000807@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Chris Wright <chrisw@redhat.com>, Gleb Natapov <gleb@redhat.com>,
	kvm@vger.kernel.org, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-fx0-f46.google.com ([209.85.161.46]:36383 "EHLO
	mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751067Ab1BJOBD (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 10 Feb 2011 09:01:03 -0500
Received: by fxm20 with SMTP id 20so1504676fxm.19
        for <kvm@vger.kernel.org>; Thu, 10 Feb 2011 06:01:02 -0800 (PST)
In-Reply-To: <4D53E155.5000807@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 02/10/2011 02:00 PM, Avi Kivity wrote:
> On 02/10/2011 02:51 PM, Anthony Liguori wrote:
>> On 02/10/2011 12:13 PM, Gleb Natapov wrote:
>>>
>>> Which spec? Even in this discussion we completely mixed different
>>> things. 440FX is not a chipset.
>>
>> Yes, it is.  It's a single silicon package with a defined pinout.  If 
>> you don't believe me, re-read the spec.
>>
>> It's a MCM with the PIIX3 being internally connected.   The 
>> connection between the i440fx and PIIX3 happens to be PCI but that's 
>> not always the case.  Sometimes it's a proprietary bus.
>
> Aren't they two distinct chips, together comprising the chip-set?
>
> One (the northbridge) converts the system bus to PCI + some extra 
> wires, the other (southbridge) bridges PCI to ISA and contains some 
> embedded ISA devices.  IIRC there are some wires between them that are 
> not PCI.

Yes, you are correct.  So I can understand an argument for:

   -device i440fx,id=pmc -device piix3,chipset=pmc

Or something like that.

Regards,

Anthony Liguori