mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "mingo@elte.hu" <mingo@elte.hu>, "hpa@zytor.com" <hpa@zytor.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	"travis@sgi.com" <travis@sgi.com>,
	"steiner@sgi.com" <steiner@sgi.com>,
	Gary Hade <garyhade@us.ibm.com>
Subject: Re: [patch] x64: Avoid irq_chip mask/unmask in fixup_irqs for interrupt-remapping
Date: Thu, 04 Jun 2009 18:18:14 -0700	[thread overview]
Message-ID: <1244164694.27006.10374.camel@localhost.localdomain> (raw)
In-Reply-To: <m1iqjbd243.fsf@fess.ebiederm.org>

On Thu, 2009-06-04 at 16:13 -0700, Eric W. Biederman wrote:
> Suresh Siddha <suresh.b.siddha@intel.com> writes:
> 
> > From: Suresh Siddha <suresh.b.siddha@intel.com>
> > Subject: x64: Avoid irq_chip mask/unmask in fixup_irqs for interrupt-remapping
> >
> > In the presence of interrupt-remapping, irqs will be migrated in the
> > process context and we don't do (and there is no need to) irq_chip mask/unmask
> > while migrating the interrupt.
> >
> > Similarly fix the fixup_irqs() that get called during cpu offline and avoid
> > calling irq_chip mask/unmask for irqs that are ok to be migrated in the
> > process context.
> >
> > While we didn't observe any race condition with the existing code,
> > this change takes complete advantage of interrupt-remapping in
> > the newer generation platforms and avoids any potential HW lockup's
> > (that often worry Eric :)
> 
> You now apparently fail to migrate the irq threads in tandem with
> the rest of the irqs.

Eric, Are you referring to Gary's issues? As far as I understand, they
don't happen in the presence of interrupt-remapping.

Can you ack this patch, as this avoid touching IO-APIC and MSI entries
and does fixup_irqs() in a much more reliable fashion.

I haven't followed Gary's couple of patches related to non
interrupt-remapping case. I will go through them and see how I can help
there.

thanks,
suresh


  reply	other threads:[~2009-06-05  1:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 18:59 Suresh Siddha
2009-06-04 23:13 ` Eric W. Biederman
2009-06-05  1:18   ` Suresh Siddha [this message]
2009-06-05  1:19     ` Suresh Siddha
2009-06-05  1:47       ` Eric W. Biederman
2009-06-06  1:19         ` Suresh Siddha
2009-06-06  2:58           ` Eric W. Biederman
2009-06-05 22:20     ` Gary Hade
2009-06-06  0:57       ` Suresh Siddha
2009-06-06 23:37         ` Gary Hade

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=1244164694.27006.10374.camel@localhost.localdomain \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@linux.intel.com \
    --cc=ebiederm@xmission.com \
    --cc=garyhade@us.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    /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

Powered by JetHome