• Yazen Ghannam's avatar
    x86/mce/AMD: Use saved threshold block info in interrupt handler · 17ef4af0
    Yazen Ghannam authored
    In the amd_threshold_interrupt() handler, we loop through every possible
    block in each bank and rediscover the block's address and if it's valid,
    e.g. valid, counter present and not locked.
    
    However, we already have the address saved in the threshold blocks list
    for each CPU and bank. The list only contains blocks that have passed
    all the valid checks.
    
    Besides the redundancy, there's also a smp_call_function* in
    get_block_address() which causes a warning when servicing the interrupt:
    
     WARNING: CPU: 0 PID: 0 at kernel/smp.c:281 smp_call_function_single+0xdd/0xf0
     ...
     Call Trace:
      <IRQ>
      rdmsr_safe_on_cpu()
      get_block_address.isra.2()
      amd_threshold_interrupt()
      smp_threshold_interrupt()
      threshold_interrupt()
    
    because we do get called in an interrupt handler *with* interrupts
    disabled, which can result in a deadlock.
    
    Drop the redundant valid checks and move the overflow check, logging and
    block reset into a separate function.
    
    Check the first block then iterate over the rest. This procedure is
    needed since the first block is used as the head of the list.
    Signed-off-by: default avatarYazen Ghannam <yazen.ghannam@amd.com>
    Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Tony Luck <tony.luck@intel.com>
    Cc: linux-edac <linux-edac@vger.kernel.org>
    Link: http://lkml.kernel.org/r/20170613162835.30750-3-bp@alien8.deSigned-off-by: default avatarIngo Molnar <mingo@kernel.org>
    17ef4af0
mce_amd.c 33.5 KB