linux-kernel - Re: [PATCH 1/3] nmi: create generic NMI backtrace implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1507161306580.18576@nanos>
Date:	Thu, 16 Jul 2015 13:07:12 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Russell King <rmk+kernel@....linux.org.uk>
cc:	linux-arm-kernel@...ts.infradead.org, x86@...nel.org,
	linux-kernel@...r.kernel.org,
	Daniel Thompson <daniel.thompson@...aro.org>
Subject: Re: [PATCH 1/3] nmi: create generic NMI backtrace implementation

On Wed, 15 Jul 2015, Russell King wrote:

> x86s NMI backtrace implementation (for arch_trigger_all_cpu_backtrace())
> is fairly generic in nature - the only architecture specific bits are
> the act of raising the NMI to other CPUs, and reporting the status of
> the NMI handler.
> 
> These are fairly simple to factor out, and produce a generic
> implementation which can be shared between ARM and x86.
> 
> Signed-off-by: Russell King <rmk+kernel@....linux.org.uk>

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/