From: Chris Wright <chrisw@sous-sol.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
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 14:20:39 -0800 [thread overview]
Message-ID: <20101130222039.GJ10050@sequoia.sous-sol.org> (raw)
In-Reply-To: <1291146762.2623.34.camel@sbsiddha-MOBL3>
* Suresh Siddha (suresh.b.siddha@intel.com) wrote:
> On Tue, 2010-11-30 at 11:28 -0800, Chris Wright wrote:
> > AFAICT, it just becomes a duplicate call in a narrow window.
> >
> > native_smp_prepare_cpus() (or APIC_init_uniprocessor()):
> > enable_IR_x2apic()
> > enable_IR()
> > enable_intr_remapping() <-- clears faults
> > default_setup_apic_routing()
> > enable_drhd_fault_handling() <-- added call to clear faults
> >
> > That's what I meant by not needed.
>
> I agree that we will call clear faults twice.
>
> With out the second clear fault, any fault in that narrow window of
> enabling intr-remapping and enabling fault handling will go unnoticed
> and block further faults getting reported.
>
> I am not sure if the first fault is necessary. I can check and remove it
> if not needed.
>
> Ideally we want to do something like:
>
> Setup fault handling
> Clear any faults
> Enable intr-remapping
Agree, that's ideal.
> But fault handling interrupt configuration depends on the apic mode that
> gets selected based on whether intr-remapping was enabled successfully
> or not. And hence we were enabling fault handling after enabling the
> intr-remapping mode.
>
> I can see if I can cleanup any of these flows for 2.6.38. For 2.6.37 and
> older kernels I would like to keep the patch simple.
Yup, makes sense.
thanks,
-chris
prev parent reply other threads:[~2010-11-30 22:21 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
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 [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=20101130222039.GJ10050@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®