linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean V Kelley <sean.v.kelley@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Kar Hin Ong <kar.hin.ong@ni.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Julia Cartwright <julia.cartwright@ni.com>,
	Keng Soon Cheah <keng.soon.cheah@ni.com>,
	Gratian Crisan <gratian.crisan@ni.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: RE: Re: "oneshot" interrupt causes another interrupt to be fired erroneously in Haswell system
Date: Mon, 10 Feb 2020 08:32:39 -0800	[thread overview]
Message-ID: <088c8f9d07fe4a36125b2f0e5aeb09defb5b5e13.camel@linux.intel.com> (raw)
In-Reply-To: <8736bjlqkg.fsf@nanos.tec.linutronix.de>

On Sun, 2020-02-09 at 16:37 +0100, Thomas Gleixner wrote:
> Sean,
> 
> Thomas Gleixner <tglx@linutronix.de> writes:
> > Sean V Kelley <sean.v.kelley@linux.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


      reply	other threads:[~2020-02-10 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31  3:53 "oneshot" interrupt causes another interrupt to be fired erroneously in Haswell system Kar Hin Ong
2019-10-31 23:05 ` Bjorn Helgaas
2019-11-01  7:46   ` Kar Hin Ong
2019-11-04 23:41   ` Thomas Gleixner
2019-11-07  9:38     ` Kar Hin Ong
2019-11-21 11:22       ` Kar Hin Ong
2020-01-15 23:05       ` Thomas Gleixner
2020-01-16  7:32         ` Kar Hin Ong
2020-01-16 10:01           ` Thomas Gleixner
2020-01-23  1:37             ` Sean V Kelley
2020-01-23 13:08               ` Thomas Gleixner
2020-02-09 15:37                 ` Thomas Gleixner
2020-02-10 16:32                   ` Sean V Kelley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=088c8f9d07fe4a36125b2f0e5aeb09defb5b5e13.camel@linux.intel.com \
    --to=sean.v.kelley@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gratian.crisan@ni.com \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=julia.cartwright@ni.com \
    --cc=kar.hin.ong@ni.com \
    --cc=keng.soon.cheah@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).