From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call minutes for Feb 8 Date: Thu, 10 Feb 2011 13:51:14 +0100 Message-ID: <4D53DF42.4030700@codemonkey.ws> References: <4D526D0D.9020507@codemonkey.ws> <4D52A86A.1030407@codemonkey.ws> <4D52F20A.7070009@codemonkey.ws> <4D539800.3070802@codemonkey.ws> <20110210090748.GD673@redhat.com> <4D53BD22.1040800@redhat.com> <20110210111354.GA21681@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org, Markus Armbruster , Blue Swirl To: Gleb Natapov Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:52870 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752822Ab1BJMvU (ORCPT ); Thu, 10 Feb 2011 07:51:20 -0500 Received: by fxm20 with SMTP id 20so1437580fxm.19 for ; Thu, 10 Feb 2011 04:51:19 -0800 (PST) In-Reply-To: <20110210111354.GA21681@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. > Again you probably mean PIIX3. Even then removing unused ide will free > one more PCI slot for my cool virtio disk array. The things is, from > code point of view, it does not cost you extra to allow composition of > ide since it is just a regular PCI device and we need to support composing > those anyway. > If this is useful, and it doesn't break guests, you can always do -device i440fx,ide=off. However, it's an exception where we're deviating from how hardware works. And that's okay, but the base modelling ought to follow real hardware closely with deviations being the exception. Regards, Anthony Liguori From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=57149 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PnVzb-00062w-06 for qemu-devel@nongnu.org; Thu, 10 Feb 2011 07:51:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PnVzU-0002Cr-86 for qemu-devel@nongnu.org; Thu, 10 Feb 2011 07:51:21 -0500 Received: from mail-fx0-f45.google.com ([209.85.161.45]:43754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PnVzT-0002CO-UY for qemu-devel@nongnu.org; Thu, 10 Feb 2011 07:51:20 -0500 Received: by fxm12 with SMTP id 12so1467559fxm.4 for ; Thu, 10 Feb 2011 04:51:19 -0800 (PST) Message-ID: <4D53DF42.4030700@codemonkey.ws> Date: Thu, 10 Feb 2011 13:51:14 +0100 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] KVM call minutes for Feb 8 References: <4D526D0D.9020507@codemonkey.ws> <4D52A86A.1030407@codemonkey.ws> <4D52F20A.7070009@codemonkey.ws> <4D539800.3070802@codemonkey.ws> <20110210090748.GD673@redhat.com> <4D53BD22.1040800@redhat.com> <20110210111354.GA21681@redhat.com> In-Reply-To: <20110210111354.GA21681@redhat.com> 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: Gleb Natapov Cc: Chris Wright , kvm@vger.kernel.org, Markus Armbruster , qemu-devel@nongnu.org, Blue Swirl , Avi Kivity 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. > Again you probably mean PIIX3. Even then removing unused ide will free > one more PCI slot for my cool virtio disk array. The things is, from > code point of view, it does not cost you extra to allow composition of > ide since it is just a regular PCI device and we need to support composing > those anyway. > If this is useful, and it doesn't break guests, you can always do -device i440fx,ide=off. However, it's an exception where we're deviating from how hardware works. And that's okay, but the base modelling ought to follow real hardware closely with deviations being the exception. Regards, Anthony Liguori