On Mon, Jun 19, 2006 at 03:06:05PM +0200, Andi Kleen wrote:
> The big question is - why do you have pages without struct page?
> It seems ... wrong.
For mspec, these are pages which come from the efi trim regions.
They are not usuable by the kernel. Dropping in a kernel TLB entry for
them does allow speculation into PROM reserved memory which will result
in corrupting PROMs memory. We have seen this in the past.
Additionally, Carsten Otte had been pursuing a do_no_pfn function to
allow execute in place to insert executable pages into an os instance
which are actually part of the physical machines memory map, but not part
of the virtual machines. Several virtual machines could share the same
physical page. I, of course, reserve the right to have gotten Carsten's
intentions completely wrong. I don't believe I have misinterpretted
the intentions of do_no_pfn as expressed on the linux-mm mailing list.
Are you saying the for the mspec pages we should extend the vmem_map,
partially populate the regions for the mspec pages, mark those pages as
uncached and reserved and then turn them over to the uncached allocator?
Seems like we have done a lot of extra work to put a struct page behind
a page which requires special handling.
For Carsten's case, how would you propose we handle that?
Thanks,
Robin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
