[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48224507.8010102@keyaccess.nl>
Date: Thu, 08 May 2008 02:10:47 +0200
From: Rene Herman <rene.herman@...access.nl>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Thomas Gleixner <tglx@...utronix.de>,
Adrian Bunk <bunk@...nel.org>,
Yinghai Lu <yhlu.kernel@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Linux Kernel <linux-kernel@...r.kernel.org>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
Pavel Machek <pavel@...e.cz>
Subject: Re: 2.6.26, PAT and AMD family 6
On 08-05-08 02:03, H. Peter Anvin wrote:
> Rene Herman wrote:
>>>
>>> Okay, that is utter nonsense. /proc/cpuinfo has always been, and
>>> will always be, the CPU *AS THE KERNEL SEES IT*. If you want
>>> something else, use x86info(1).
>>
>> What a lovely way of syncing reality with your definitions. The kernel
>> _does_ see that my CPU features PAT, it just refuses to use it because
>> it doesn't trust it enough. Vital difference. Maybe not to the kernel,
>> but definitely to me, the user. /proc/cpuinfo is a user interface.
>>
>
> No, /proc/cpuinfo is informing the user about the kernel's view of the
> CPU.
And again, the kernel DOES see that my CPU features PAT, it just refuses
to use it.
Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists