Re: PCI memory allocation bug with CONFIG_HIGHMEM

[Mika Penttilä]

Andi Kleen wrote:

> 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.

But AGP aperture is controlled with the standard APBASE pci base 
register, so you always know where it is, can relocate it and reserve 
address space for it. Of course there may exist other uncontrollable hw, 
which may cause problems.

> 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
>  
--Mika


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