Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-15 Thread Bill Davidsen
[EMAIL PROTECTED] wrote: From: Theodore Tso <[EMAIL PROTECTED]> Date: Thu, Dec 14, 2006 at 10:17:45AM -0500 Remove an (incorrect) assertion that NOHIGHMEM is right for more users, since most systems are coming with at least 1G of memory these days, and even some laptops have up 4G of memory.

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-15 Thread Bill Davidsen
[EMAIL PROTECTED] wrote: From: Theodore Tso [EMAIL PROTECTED] Date: Thu, Dec 14, 2006 at 10:17:45AM -0500 Remove an (incorrect) assertion that NOHIGHMEM is right for more users, since most systems are coming with at least 1G of memory these days, and even some laptops have up 4G of memory.

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Alistair John Strachan
On Thursday 14 December 2006 15:37, Theodore Tso wrote: > > + 1 Gigabyte or more total physical RAM, answer "off" here. > > I don't think your proposed wording (1 gigabyte or more) versus (more > than 1 gigabyte) doesn't really change the sense of this. It does, because if you have exactly 1G

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Avi Kivity
Theodore Tso wrote: + 1 Gigabyte or more total physical RAM, answer "off" here. I don't think your proposed wording (1 gigabyte or more) versus (more than 1 gigabyte) doesn't really change the sense of this. If we want to be even more explicit about this, then if the CPU level

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Arjan van de Ven
On Thu, 2006-12-14 at 10:37 -0500, Theodore Tso wrote: > > + 1 Gigabyte or more total physical RAM, answer "off" here. > > > > I don't think your proposed wording (1 gigabyte or more) versus (more > than 1 gigabyte) doesn't really change the sense of this. > > If we want to be even more

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Arjan van de Ven
On Thu, 2006-12-14 at 10:17 -0500, Theodore Tso wrote: > > > I'd be happy to know how to enable it. > > > > CONFIG_HIGHMEM64G=y > > This is not at all obvious from arch/i386/Kconfig. Maybe we should > fix this? looks better; maybe add how to look for "pae" and "nx" in the /proc/cpuinfo flags

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread thunder7
From: Theodore Tso <[EMAIL PROTECTED]> Date: Thu, Dec 14, 2006 at 10:17:45AM -0500 > > Remove an (incorrect) assertion that NOHIGHMEM is right for more > users, since most systems are coming with at least 1G of memory these > days, and even some laptops have up 4G of memory. Given this (on a

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Theodore Tso
> + 1 Gigabyte or more total physical RAM, answer "off" here. > I don't think your proposed wording (1 gigabyte or more) versus (more than 1 gigabyte) doesn't really change the sense of this. If we want to be even more explicit about this, then if the CPU level selected by the user is

[PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Theodore Tso
> > I'd be happy to know how to enable it. > > CONFIG_HIGHMEM64G=y This is not at all obvious from arch/i386/Kconfig. Maybe we should fix this? - Ted Add an explanation that HIGHMEM64G is needed in order to get support for the NX feature. Remove an

[PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Theodore Tso
I'd be happy to know how to enable it. CONFIG_HIGHMEM64G=y This is not at all obvious from arch/i386/Kconfig. Maybe we should fix this? - Ted Add an explanation that HIGHMEM64G is needed in order to get support for the NX feature. Remove an

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Theodore Tso
+ 1 Gigabyte or more total physical RAM, answer off here. I don't think your proposed wording (1 gigabyte or more) versus (more than 1 gigabyte) doesn't really change the sense of this. If we want to be even more explicit about this, then if the CPU level selected by the user is greater

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread thunder7
From: Theodore Tso [EMAIL PROTECTED] Date: Thu, Dec 14, 2006 at 10:17:45AM -0500 Remove an (incorrect) assertion that NOHIGHMEM is right for more users, since most systems are coming with at least 1G of memory these days, and even some laptops have up 4G of memory. Given this (on a system

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Arjan van de Ven
On Thu, 2006-12-14 at 10:17 -0500, Theodore Tso wrote: I'd be happy to know how to enable it. CONFIG_HIGHMEM64G=y This is not at all obvious from arch/i386/Kconfig. Maybe we should fix this? looks better; maybe add how to look for pae and nx in the /proc/cpuinfo flags line ? -- if

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Arjan van de Ven
On Thu, 2006-12-14 at 10:37 -0500, Theodore Tso wrote: + 1 Gigabyte or more total physical RAM, answer off here. I don't think your proposed wording (1 gigabyte or more) versus (more than 1 gigabyte) doesn't really change the sense of this. If we want to be even more explicit about

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Avi Kivity
Theodore Tso wrote: + 1 Gigabyte or more total physical RAM, answer off here. I don't think your proposed wording (1 gigabyte or more) versus (more than 1 gigabyte) doesn't really change the sense of this. If we want to be even more explicit about this, then if the CPU level

Re: [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options

2006-12-14 Thread Alistair John Strachan
On Thursday 14 December 2006 15:37, Theodore Tso wrote: + 1 Gigabyte or more total physical RAM, answer off here. I don't think your proposed wording (1 gigabyte or more) versus (more than 1 gigabyte) doesn't really change the sense of this. It does, because if you have exactly 1G of