linux-kernel - RE: [RFC] ACPI, APEI, Generic Hardware Error Source POLL/IRQ/NMI notification type support

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: <987664A83D2D224EAE907B061CE93D530193C9D504@orsmsx505.amr.corp.intel.com>
Date:	Wed, 15 Dec 2010 08:40:09 -0800
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Huang, Ying" <ying.huang@...el.com>, Len Brown <lenb@...nel.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: RE: [RFC] ACPI, APEI, Generic Hardware Error Source POLL/IRQ/NMI
 notification type support

>Because the memory area used to transfer hardware error information
>from BIOS to Linux can be determined only in NMI, IRQ or timer
>handler, but general ioremap can not be used in atomic context, so a
>special version of atomic ioremap is implemented for that.
>
>Known issue:
>
>- Error information can not be printed for recoverable errors notified
>  via NMI, because printk is not NMI-safe. Will fix this via delay
>  printing to IRQ context via irq_work or make printk NMI-safe.

Would it be possible to defer the "ioremap" to a work queue too? Then
we wouldn't need the special versions of ioremap.

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