Date: 6 Jan 2004 10:44:42 +0100
Date: Tue, 6 Jan 2004 10:44:42 +0100
From: Andi Kleen <ak@colin2.muc.de>
To: Mika Penttil? <mika.penttila@kolumbus.fi>
Cc: Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@muc.de>,
       David Hinds <dhinds@sonic.net>, linux-kernel@vger.kernel.org
Subject: Re: PCI memory allocation bug with CONFIG_HIGHMEM
Message-ID: <20040106094442.GB44540@colin2.muc.de>
References: <1aJdi-7TH-25@gated-at.bofh.it> <m37k054uqu.fsf@averell.firstfloor.org> <Pine.LNX.4.58.0401051937510.2653@home.osdl.org> <20040106040546.GA77287@colin2.muc.de> <Pine.LNX.4.58.0401052100380.2653@home.osdl.org> <20040106081203.GA44540@colin2.muc.de> <3FFA7BB9.1030803@kolumbus.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FFA7BB9.1030803@kolumbus.fi>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1096
Lines: 30

On Tue, Jan 06, 2004 at 11:11:21AM +0200, Mika Penttil? wrote:
> 
> 
> Andi Kleen wrote:
> 
> >>If you ahve a proper e820 map, then it should work correctly, with 
> >>anything that is RAM being marked as such (or being marked as "reserved").
> >>   
> >>
> >
> >Every e820 map i've seen did not have the AGP aperture marked reserved.
> >
> Why should it? It's not ram, and the aperture is marked as reserved 
> while doing PCI resource assignment/reservation.

It implies that you cannot just put your IO mappings
into any holes. Because something else like the aperture may 
be already there.

In my opinion it would have been cleaner if the aperture had always
an reserved entry in the e820 map. Or better all usable holes get
an special entry. Then you could actually reliable allocate IO space
 on your own. Currently it's just impossible.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/