[lkml]   [2010]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC 4/6] x86, NMI, Rewrite NMI handler
    On 09.09.10 22:51:03, Huang Ying wrote:
    > DIE_NMI_IPI is used to process CPU specific NMI sources, such as perf
    > event, oprofile, crash IPI, etc. While DIE_NMI is used to process
    > non-CPU-specific NMI sources, such as APEI (ACPI Platform Error
    > Interface) GHES (Generic Hardware Error Source), etc.
    > DIE_NMI_IPI must be processed before DIE_NMI. For example, perf event
    > trigger a NMI on CPU 1, at the same time, APEI GHES trigger another
    > NMI on CPU 0. If DIE_NMI is processed before DIE_NMI_IPI, it is
    > possible that APEI GHES is processed on CPU 1, while unknown NMI is
    > gotten on CPU 0.

    Ingo, Peter,

    couldn't this be the reason for the regression we are observing with
    unhandled nmis?


    Advanced Micro Devices, Inc.
    Operating System Research Center

     \ /
      Last update: 2010-09-13 03:21    [W:0.025 / U:99.476 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site