linux-kernel - Re: [PATCH 0/2] Fix dmar fault interrupt problems

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, 30 Nov 2010 10:13:14 -0800
From:	Chris Wright <chrisw@...s-sol.org>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"hpa@...or.com" <hpa@...or.com>, "x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"indou.takao@...fujitsu.com" <indou.takao@...fujitsu.com>
Subject: Re: [PATCH 0/2] Fix dmar fault interrupt problems

* Suresh Siddha (suresh.b.siddha@...el.com) wrote:
> On Tue, 2010-11-30 at 00:28 -0800, Kenji Kaneshige wrote:
> > Hi,
> > 
> > Here are patches to fix the following problems regarding dmar fault interrupt.
> > 
> > - No dmar fault event is notified in x2apic cluster mode
> > - Changing IRQ affinity of dmar fault interrupt causes "No irq handler
> >   for vector (irq XX)" message and dmar fault interrupts are never
> >   notified after that.
> 
> Kenji, In addition to these two, there are couple of more patches that
> are needed to fix the kexec/kdump issue that we are debugging on RH
> bugzilla.
> 
> I will post all these 4 patches shortly. I already noticed and queued
> the second patch (dmar irq migration)  you mentioned.

And one of them (the additional call to flushing existing dmar faults)
is not needed.  So the quirk plus ensuring ir faults show up as msi
interrupts should be sufficient.

thanks,
-chris
--
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/