linux-kernel - Re: [PATCH] x86: Recover timer_ack lost in the merge of the NMI watchdog

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] [day] [month] [year] [list]

Message-ID: <20080713094434.GA32578@elte.hu>
Date:	Sun, 13 Jul 2008 11:44:34 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] x86: Recover timer_ack lost in the merge of the NMI
	watchdog


* Maciej W. Rozycki <macro@...ux-mips.org> wrote:

> On Fri, 11 Jul 2008, Ingo Molnar wrote:
> 
> > i've applied your fixes to tip/x86/core:
> > 
> >  Maciej W. Rozycki (4):
> >       x86: L-APIC: Set IRQ0 as edge-triggered
> >       x86: L-APIC: Always fully configure IRQ0
> >       x86: I/O APIC: Never configure IRQ2
> >       x86: Recover timer_ack lost in the merge of the NMI watchdog
> 
> Thanks, please apply "x86: I/O APIC: Remove an IRQ2-mask hack" on top 
> of these.  Then what currently comprises 
> dmi_ignore_irq0_timer_override() can be done more properly as soon as 
> we know how to get information about INTIN0/2 configurations from the 
> SB400.  Furthermore, following considerations in the other mail, I 
> think the HPET driver should use the notion of ISA IRQ numbers by 
> mapping them appropriately from I/O APIC pin numbers.  Reusing 
> pin_2_irq() for this purpose seems a reasonable way of doing this to 
> me.

applied to tip/x86/core, thanks Maciej.

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