lkml.org 
[lkml]   [2000]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: HIGH MEMORY access
Ingo Molnar wrote:
>
> On Fri, 3 Mar 2000, Manfred Spraul wrote:
>
> > Now I'm confused: I thought that ioremap() should be used for reserved
> > memory, and kmap() for normal memory (e820: ram) with
> > page->virtual==NULL.
>
> well you can use kmap() for anything, not just high memory. I suggested
> kmap() because ioremap() relies on a working allocator and other
> higher-level structures - kmap() certainly works better for smaller
> structures such as the MP-table.

Have you ever tried to do that?
kmap() is a nop if your kernel is not compiled for CONFIG_HIGHMEM, and
kmap_atomic() doesn't even exist.

It seems we should add a vremap_boot() for the boot process.
Btw, can the MP tables cross page boundaries? kmap() would make parsing
such tables extremely difficult.

--
Manfred



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

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.061 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site