• Steven Honeyman's avatar
    x86, CPU: Fix trivial printk formatting issues with dmesg · f94fe119
    Steven Honeyman authored
    dmesg (from util-linux) currently has two methods for reading the kernel
    message ring buffer: /dev/kmsg and syslog(2). Since kernel 3.5.0 kmsg
    has been the default, which escapes control characters (e.g. new lines)
    before they are shown.
    
    This change means that when dmesg is using /dev/kmsg, a 2 line printk
    makes the output messy, because the second line does not get a
    timestamp.
    
    For example:
    
    [    0.012863] CPU0: Thermal monitoring enabled (TM1)
    [    0.012869] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
    Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
    [    0.012958] Freeing SMP alternatives memory: 28K (ffffffff81d86000 - ffffffff81d8d000)
    [    0.014961] dmar: Host address width 39
    
    Because printk.c intentionally escapes control characters, they should
    not be there in the first place. This patch fixes two occurrences of
    this.
    Signed-off-by: default avatarSteven Honeyman <stevenhoneyman@gmail.com>
    Link: https://lkml.kernel.org/r/1414856696-8094-1-git-send-email-stevenhoneyman@gmail.com
    [ Boris: make cpu_detect_tlb() static, while at it. ]
    Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
    f94fe119
intel.c 21.7 KB