mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"indou.takao@jp.fujitsu.com" <indou.takao@jp.fujitsu.com>
Subject: Re: [PATCH 0/2] Fix dmar fault interrupt problems
Date: Tue, 30 Nov 2010 10:13:14 -0800	[thread overview]
Message-ID: <20101130181314.GH10050@sequoia.sous-sol.org> (raw)
In-Reply-To: <1291140553.2623.10.camel@sbsiddha-MOBL3>

* Suresh Siddha (suresh.b.siddha@intel.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

  reply	other threads:[~2010-11-30 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  8:28 Kenji Kaneshige
2010-11-30  8:30 ` [PATCH 1/2] dmar: fix fault interrupt setup Kenji Kaneshige
2010-11-30 20:18   ` Suresh Siddha
2010-12-01  5:13     ` Kenji Kaneshige
2010-11-30  8:32 ` [PATCH 2/2] dmar: Fix dmar interrupt affinity handling Kenji Kaneshige
2010-11-30 18:09 ` [PATCH 0/2] Fix dmar fault interrupt problems Suresh Siddha
2010-11-30 18:13   ` Chris Wright [this message]
2010-11-30 18:20     ` Suresh Siddha
2010-11-30 19:28       ` Chris Wright
2010-11-30 19:52         ` Suresh Siddha
2010-11-30 22:20           ` Chris Wright

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=20101130181314.GH10050@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=hpa@zytor.com \
    --cc=indou.takao@jp.fujitsu.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=suresh.b.siddha@intel.com \
    --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
all inboxes | Powered by JetHome®