linux-kernel - Re: [PATCH] - Add IOAPIC NMI support on x86

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]

Date:	Tue, 19 Jun 2007 08:34:19 -0500 (CDT)
From:	John Keller <jpk@....com>
To:	andi@...stfloor.org (Andi Kleen)
Cc:	jpk@....com (John Keller), linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, steiner@....com
Subject: Re: [PATCH] - Add IOAPIC NMI support on x86_64

>
> John Keller <jpk@....com> writes:
>
> > Add support for IOAPIC NMI interrupts on x86_64.
> >
> > Changes include the following:
> >
> >   - Obtain the NMI IOAPIC info via an ACPI NMI SRC structure that is
> >     part of the MADT, and program the IOAPIC redirection register.
> >     The NMI SRC struct will contain the GSI of the NMI interrupt.
> >
> >   - Setup irq_desc[] and irq_2_pin[] entries for the NMI interrupt irq,
> >     which will be used by the generic mask/unmask routines. This will
> >     allow a driver to enable/disable the NMI interrupt via
> >     enable/disable_irq().
>
> What's the motivation for this patch?

 In our specific case, a loadable driver will register to process
 the NMI generated by a timer device on the IOAPIC pin. The driver
 will need to unmask/mask the NMI interrupt at init/exit time.

 The timer NMI interrupt will be used to synchronize cluster nodes.

John


>
> -Andi
>

-
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/