summaryrefslogtreecommitdiffstats
path: root/fs/proc/nommu.c
diff options
context:
space:
mode:
authorRoland Dreier <rdreier@cisco.com>2009-09-23 15:35:35 -0700
committerIngo Molnar <mingo@elte.hu>2009-09-24 11:35:19 +0200
commite23a8b6a8f319c0f08b6ccef2dccbb37e7603dc2 (patch)
treeb2026dfe1507925bb26fbe12d9598832363e0c9c /fs/proc/nommu.c
parentea01c0d7315d6e3218fd22a6947c5b09305fcf65 (diff)
downloadblackbird-op-linux-e23a8b6a8f319c0f08b6ccef2dccbb37e7603dc2.tar.gz
blackbird-op-linux-e23a8b6a8f319c0f08b6ccef2dccbb37e7603dc2.zip
x86: Reduce verbosity of "PAT enabled" kernel message
On modern systems, the kernel prints the message x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 once for every CPU. This gets kind of ridiculous on huge systems; for example, on a 64-thread system I was lucky enough to get: dmesg| grep 'PAT enabled' | wc 64 704 5174 There is already a BUG() if non-boot CPUs have PAT capabilities that don't match the boot CPU, so just print the message on the boot CPU. (I kept the print after the wrmsrl() that enables PAT, so that the log output continues to mean that the system survived enabling PAT on the boot CPU) Signed-off-by: Roland Dreier <rolandd@cisco.com> Cc: Suresh Siddha <suresh.b.siddha@intel.com> Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> LKML-Reference: <adavdj92sso.fsf@cisco.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'fs/proc/nommu.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud