public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Hade <garyhade@us.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Gary Hade <garyhade@us.ibm.com>,
	mingo@elte.hu, mingo@redhat.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, x86@kernel.org, ebiederm@xmission.com,
	yinghai@kernel.org, lcm@us.ibm.com
Subject: Re: [RESEND] [PATCH v2] [BUGFIX] x86/x86_64: fix CPU offlining triggered "active" device IRQ interrruption
Date: Wed, 3 Jun 2009 09:40:13 -0700	[thread overview]
Message-ID: <20090603164013.GA7566@us.ibm.com> (raw)
In-Reply-To: <4A26014F.4070207@zytor.com>

On Tue, Jun 02, 2009 at 09:51:27PM -0700, H. Peter Anvin wrote:
> Gary Hade wrote:
> > Impact: Eliminates an issue that can leave the system in an
> >         unusable state.
> > 
> > This patch addresses an issue where device generated IRQs
> > are no longer seen by the kernel following IRQ affinity
> > migration while the device is generating IRQs at a high rate.
> > 
> 
> This patch doesn't seem to apply to current mainline.
> 
> What is your base?

git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
which Ingo encouraged me to use because it contained some of 
Yinghai Lu's recent changes that hadn't reached mainline yet.

Gary

-- 
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503  IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc

  reply	other threads:[~2009-06-03 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 19:32 [RESEND] [PATCH v2] [BUGFIX] x86/x86_64: fix CPU offlining triggered "active" device IRQ interrruption Gary Hade
2009-06-03  4:51 ` H. Peter Anvin
2009-06-03 16:40   ` Gary Hade [this message]
2009-06-03 12:03 ` Eric W. Biederman
2009-06-03 17:06   ` Gary Hade
2009-06-03 21:13     ` Eric W. Biederman
2009-06-04 20:04       ` Gary Hade
2009-06-04 21:17         ` Gary Hade
2009-06-04 23:16         ` Eric W. Biederman
2009-06-03 12:27 ` Eric W. Biederman

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=20090603164013.GA7566@us.ibm.com \
    --to=garyhade@us.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --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