> Got a question. How will kernel continue to run if we unmap the kernel
> text/data region mappings?
Normally it shouldn't be in the same 2MB area as the aperture (which
is the only thing that is unmapped). The problem is mostly
the rest of the 40MB kernel mapping.
-Andi
--
To unsubscribe
On Thu, Jan 03, 2008 at 06:26:57PM +0100, Andi Kleen wrote:
>
> This was a long standing obscure problem in the relocatable kernel. The
> AMD GART driver needs to unmap part of the GART in the kernel direct mapping
> to
> prevent cache corruption. With the relocatable kernel it is in theory
>
This was a long standing obscure problem in the relocatable kernel. The
AMD GART driver needs to unmap part of the GART in the kernel direct mapping to
prevent cache corruption. With the relocatable kernel it is in theory possible
that the separate kernel text mapping straddles that area too.
This was a long standing obscure problem in the relocatable kernel. The
AMD GART driver needs to unmap part of the GART in the kernel direct mapping to
prevent cache corruption. With the relocatable kernel it is in theory possible
that the separate kernel text mapping straddles that area too.
On Thu, Jan 03, 2008 at 06:26:57PM +0100, Andi Kleen wrote:
This was a long standing obscure problem in the relocatable kernel. The
AMD GART driver needs to unmap part of the GART in the kernel direct mapping
to
prevent cache corruption. With the relocatable kernel it is in theory
Got a question. How will kernel continue to run if we unmap the kernel
text/data region mappings?
Normally it shouldn't be in the same 2MB area as the aperture (which
is the only thing that is unmapped). The problem is mostly
the rest of the 40MB kernel mapping.
-Andi
--
To unsubscribe from
6 matches
Mail list logo
