From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [Qemu-devel] [RFC v5 86/86] 440fx: fix PAM, PCI holes Date: Mon, 25 Jul 2011 16:35:58 +0300 Message-ID: <20110725133558.GH4404@redhat.com> References: <1311180636-17012-1-git-send-email-avi@redhat.com> <1311180636-17012-87-git-send-email-avi@redhat.com> <4E2D6A97.9050606@codemonkey.ws> <4E2D6C45.5030308@redhat.com> <20110725131728.GD4404@redhat.com> <4E2D6F6C.5070301@redhat.com> <4E2D702F.6010400@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=cp1255 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32040 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751212Ab1GYNgB convert rfc822-to-8bit (ORCPT ); Mon, 25 Jul 2011 09:36:01 -0400 Content-Disposition: inline In-Reply-To: <4E2D702F.6010400@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Jul 25, 2011 at 04:31:27PM +0300, Avi Kivity wrote: > On 07/25/2011 04:28 PM, Avi Kivity wrote: > >On 07/25/2011 04:17 PM, Gleb Natapov wrote: > >>On Mon, Jul 25, 2011 at 04:14:45PM +0300, Avi Kivity wrote: > >>> On 07/25/2011 04:07 PM, Anthony Liguori wrote: > >>> >On 07/20/2011 11:50 AM, Avi Kivity wrote: > >>> >>The current implementation of PAM and the PCI holes is > >>broken in several > >>> >>ways: > >>> >> > >>> >> - PCI BARs are not restricted to the PCI hole (a BAR may > >>hide memory) > >>> > > >>> >Technically, a BAR can be mapped to any non-RAM memory location. > >>> > >>> I understood TOM (Top Of Memory) to be fixed - can't find a regi= ster > >>> for it - but maybe I misread the spec. > >>> > >>PIIX3 spec: > >> > >>2.2.11. TOM=97TOP OF MEMORY REGISTER (Function 0) > >>Address Offset: 69h > >>Default Value: 02h > >>Attribute: Read/Write > >> > > > >What's it doing in PIIX3? Is it the same TOM? > > >=20 > That's the ISA TOM (15MB hole and friends). >=20 Correct. What about: 3.2.19. DRB[0:7] DRAM ROW BOUNDARY REGISTERS from 440fx spec? -- Gleb. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43156) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QlLKI-00010M-U8 for qemu-devel@nongnu.org; Mon, 25 Jul 2011 09:36:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QlLKD-00038H-Hm for qemu-devel@nongnu.org; Mon, 25 Jul 2011 09:36:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:16389) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QlLKD-00038B-9S for qemu-devel@nongnu.org; Mon, 25 Jul 2011 09:36:01 -0400 Date: Mon, 25 Jul 2011 16:35:58 +0300 From: Gleb Natapov Message-ID: <20110725133558.GH4404@redhat.com> References: <1311180636-17012-1-git-send-email-avi@redhat.com> <1311180636-17012-87-git-send-email-avi@redhat.com> <4E2D6A97.9050606@codemonkey.ws> <4E2D6C45.5030308@redhat.com> <20110725131728.GD4404@redhat.com> <4E2D6F6C.5070301@redhat.com> <4E2D702F.6010400@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=cp1255 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <4E2D702F.6010400@redhat.com> Subject: Re: [Qemu-devel] [RFC v5 86/86] 440fx: fix PAM, PCI holes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org On Mon, Jul 25, 2011 at 04:31:27PM +0300, Avi Kivity wrote: > On 07/25/2011 04:28 PM, Avi Kivity wrote: > >On 07/25/2011 04:17 PM, Gleb Natapov wrote: > >>On Mon, Jul 25, 2011 at 04:14:45PM +0300, Avi Kivity wrote: > >>> On 07/25/2011 04:07 PM, Anthony Liguori wrote: > >>> >On 07/20/2011 11:50 AM, Avi Kivity wrote: > >>> >>The current implementation of PAM and the PCI holes is > >>broken in several > >>> >>ways: > >>> >> > >>> >> - PCI BARs are not restricted to the PCI hole (a BAR may > >>hide memory) > >>> > > >>> >Technically, a BAR can be mapped to any non-RAM memory location. > >>> > >>> I understood TOM (Top Of Memory) to be fixed - can't find a register > >>> for it - but maybe I misread the spec. > >>> > >>PIIX3 spec: > >> > >>2.2.11. TOM=97TOP OF MEMORY REGISTER (Function 0) > >>Address Offset: 69h > >>Default Value: 02h > >>Attribute: Read/Write > >> > > > >What's it doing in PIIX3? Is it the same TOM? > > >=20 > That's the ISA TOM (15MB hole and friends). >=20 Correct. What about: 3.2.19. DRB[0:7] DRAM ROW BOUNDARY REGISTERS =66rom 440fx spec? -- Gleb.