Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository
Switch branch/tag
  • xcap-capability-linux
  • arch
  • x86
  • kernel
  • kgdb.c
Find file BlameHistoryPermalink
  • Jan Kiszka's avatar
    kgdb, x86: Avoid invoking kgdb_nmicallback twice per NMI · e85ceae9
    Jan Kiszka authored Oct 06, 2008
    
    
    Stress-testing KVM's latest NMI support with kgdbts inside an SMP guest,
    I came across spurious unhandled NMIs while running the singlestep test.
    Looking closer at the code path each NMI takes when KGDB is enabled, I
    noticed that kgdb_nmicallback is called twice per event: One time via
    DIE_NMI_IPI notification, the second time on DIE_NMI. Removing the first
    invocation cures the unhandled NMIs here.
    Signed-off-by: default avatarJan Kiszka <jan.kiszka@siemens.com>
    Signed-off-by: default avatarJason Wessel <jason.wessel@windriver.com>
    e85ceae9

Replace kgdb.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.