On Fri, Jun 08, 2007 at 10:07:52AM +0200, Mikael Pettersson wrote:
> Is this really needed? I can see why VMSPLIT_{2,3}G_OPT would
> depend on !HIGHMEM, but why would they depend on !X86_PAE?The only reason they depend on !HIGHMEM is because handling for 1GB-unaligned splits is unimplemented for PAE, which formerly only occurred in conjunction with HIGHMEM64G. That said, they were oriented toward avoiding highmem on laptops, hence the broader !HIGHMEM constraint. The entire point of the patch is to add an option to use PAE without highmem for the purposes of NX and secondarily expanded swapspace, at which point CONFIG_VMSPLIT_[23]G_OPT need some other way besides !HIGHMEM to exclude PAE, such as specifying !X86_PAE directly. -- wli - 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/
