mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "Zhang, Lin-Bao (Linux Kernel R&D)" <linbao.zhang@hp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"Croxon, Nigel" <nigel.croxon@hp.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
	"Sakkinen, Jarkko" <jarkko.sakkinen@intel.com>,
	"joerg.roedel@amd.com" <joerg.roedel@amd.com>,
	"agordeev@redhat.com" <agordeev@redhat.com>,
	"yinghai@kernel.org" <yinghai@kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )
Date: Wed, 10 Oct 2012 17:07:19 -0700	[thread overview]
Message-ID: <1349914040.3042.12.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <92645B27BF79D04FBD2B0F8494FFD0F90FE41E@G2W2429.americas.hpqcorp.net>

On Wed, 2012-10-10 at 00:26 +0000, Zhang, Lin-Bao (Linux Kernel R&D)
wrote:

> So , we can think ,as your patch , during the window , IO-apic is
> useless or we can think IO-APIC doesn't exist ? 
> Could you mind please sharing your design details ? thanks very much! 

Between the window of interrupt-remapping enabled and the masked IO-APIC
RTE's are configured properly, linux kernel doesn't wait/depend on any
external interrupts.

> > Can you please apply the appended patch to 2.6.32 kernel and see if the issue
> > you mentioned gets fixed? If so, we can ask the -stable and OSV's teams to
> > pick up this fix.
> Yes , it can resolve current issue. 

Thanks for testing it out.

I will add the appropriate changelog and send the patch out (to 2.6.32
stable and OSV kernels) with your "Tested-by:" if you are ok.

thanks,
suresh


  reply	other threads:[~2012-10-11  0:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08  4:53 Zhang, Lin-Bao (Linux Kernel R&D)
2012-10-08 23:57 ` Suresh Siddha
2012-10-10  0:26   ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-10-11  0:07     ` Suresh Siddha [this message]
2012-10-11  3:52       ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-10-11  5:26         ` H. Peter Anvin
2012-10-11 15:32           ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-10-10 23:02   ` Zhang, Lin-Bao (Linux Kernel R&D)
2012-10-11  0:01     ` Suresh Siddha
2012-10-11 16:46       ` Zhang, Lin-Bao (Linux Kernel R&D)
  -- strict thread matches above, loose matches on Subject: below --
2012-09-21  7:20 Zhang, Lin-Bao (Linux Kernel R&D)

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=1349914040.3042.12.camel@sbsiddha-desk.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=agordeev@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=jarkko.sakkinen@intel.com \
    --cc=joerg.roedel@amd.com \
    --cc=linbao.zhang@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nigel.croxon@hp.com \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yinghai@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®