| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 5 May 2008 18:55:04 +0200 From: Frans Pop <elendil@...net.nl> To: "Yinghai Lu" <yhlu.kernel@...il.com> Cc: "Jesse Barnes" <jesse.barnes@...el.com>, "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>, linux-kernel@...r.kernel.org, "Ingo Molnar" <mingo@...e.hu>, "Packard, Keith" <keith.packard@...el.com> Subject: Re: [git head] Should X86_PAT really default to yes? On Sunday 04 May 2008, Yinghai Lu wrote: > can you boot with pat=off and send out /proc/mtrr? Hmmm. Is 'pat=off' supposed to do anything? With a default boot I see: kernel: Command line: root=/dev/mapper/main-root ro vga=791 [...] kernel: x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106 And with 'pat=off' I get the same: kernel: Command line: root=/dev/mapper/main-root ro vga=791 pat=off [...] kernel: x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106 Anyway, the info in /proc/mtrr is identical with and without the option, and is also identical to what I get with 2.6.25.1: $ cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 reg01: base=0x7f800000 (2040MB), size= 8MB: uncachable, count=1 reg02: base=0x7f700000 (2039MB), size= 1MB: uncachable, count=1 reg03: base=0x80000000 (2048MB), size= 256MB: write-combining, count=1 Cheers, FJP -- 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