All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Waiman Long <longman@redhat.com>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v2] x86/nmi: Add an emergency handler in nmi_desc & use it in nmi_shootdown_cpus()
Date: Wed, 04 Dec 2024 14:10:27 +0100	[thread overview]
Message-ID: <87h67jsif0.ffs@tglx> (raw)
In-Reply-To: <20241203150732.182065-1-longman@redhat.com>

On Tue, Dec 03 2024 at 10:07, Waiman Long wrote:
> +	/*
> +	 * Call the emergency handler first, if set
> +	 * Emergency handler is not traced or checked by nmi_check_duration().
> +	 */
> +	ehandler = READ_ONCE(desc->emerg_handler);
> +	if (ehandler)
> +		handled = ehandler(type, regs);

Shouldn't this just stop processing right here?

Thanks,

        tglx

  parent reply	other threads:[~2024-12-04 13:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 15:07 [PATCH v2] x86/nmi: Add an emergency handler in nmi_desc & use it in nmi_shootdown_cpus() Waiman Long
2024-12-04  1:00 ` Rik van Riel
2024-12-04  1:39   ` Waiman Long
2024-12-04  7:58 ` kernel test robot
2024-12-04 13:10 ` Thomas Gleixner [this message]
2024-12-04 17:23   ` Waiman Long
2024-12-04 18:03     ` Thomas Gleixner
2024-12-04 19:28       ` Waiman Long
2024-12-05  4:01         ` Waiman Long
2024-12-05 13:12           ` Thomas Gleixner
     [not found]             ` <1166fd72-8a4a-489f-9de5-7c06b70b0ad4@redhat.com>
2024-12-05 18:17               ` Thomas Gleixner
2024-12-06  4:16                 ` Waiman Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h67jsif0.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.