linux-kernel - Re: RE: Re: "oneshot" interrupt causes another interrupt to be fired erroneously in Haswell system

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: <088c8f9d07fe4a36125b2f0e5aeb09defb5b5e13.camel@linux.intel.com>
Date:   Mon, 10 Feb 2020 08:32:39 -0800
From:   Sean V Kelley <sean.v.kelley@...ux.intel.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Kar Hin Ong <kar.hin.ong@...com>,
        Bjorn Helgaas <helgaas@...nel.org>
Cc:     linux-rt-users <linux-rt-users@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "x86@...nel.org" <x86@...nel.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "H. Peter Anvin" <hpa@...or.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Julia Cartwright <julia.cartwright@...com>,
        Keng Soon Cheah <keng.soon.cheah@...com>,
        Gratian Crisan <gratian.crisan@...com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: RE: Re: "oneshot" interrupt causes another interrupt to be
 fired erroneously in Haswell system

On Sun, 2020-02-09 at 16:37 +0100, Thomas Gleixner wrote:
> Sean,
> 
> Thomas Gleixner <tglx@...utronix.de> writes:
> > Sean V Kelley <sean.v.kelley@...ux.intel.com> writes:
> > > So I will ensure we actually create useful information pointing
> > > to this
> > > behavior either in kernel docs or online as in a white paper or
> > > both.
> > 
> > Great.
> > 
> > > > As we have already quirks in drivers/pci/quirks.c which handle
> > > > the
> > > > same issue on older chipsets, we really should add one for
> > > > these kind
> > > > of systems to avoid fiddling with the BIOS (which you can, but
> > > > most
> > > > people cannot).
> > > Agreed, and I will follow-up with Kar Hin Ong to get them added.
> > 
> > Much appreciated.
> 
> Any update on this?

Hi Thomas,

I've been working with Kar Hin in attempting to follow a similar
pattern to the earlier PCI quirks done with ESB / ESB2 chipsets.
However, the optional INTX routing table which was a part of the
original quirk done about 10 years ago changed by the time these
Haswell PCH arrived.  The later PCH aligned with the BIOS switch
becoming available and the deprecation of the bypass routing.  We're
testing a few more things, and I hope to have a conclusion this week.

Thanks,

Sean

> 
> Thanks,
> 
>         tglx