All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	Yinghai Lu <yhlu.kernel@gmail.com>,
	mingo@elte.hu, ak@suse.de, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, "Zou,
	Nanhai" <nanhai.zou@intel.com>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Packard, Keith" <keith.packard@intel.com>
Subject: Re: [patch] x86_64, irq: check remote IRR bit before migrating level triggered irq
Date: Fri, 18 May 2007 12:18:13 -0700	[thread overview]
Message-ID: <20070518191813.GC28957@linux-os.sc.intel.com> (raw)
In-Reply-To: <m1wsz6ymyv.fsf@ebiederm.dsl.xmission.com>

On Fri, May 18, 2007 at 12:02:16PM -0700, Eric W. Biederman wrote:
> I will look closer but I do believe that from the ioapic to the cpu the 2.6.21
> code should be fairly robust with respect to inflight messages from the ioapic
> to the local apics and the cpus.  What I failed to consider were inflight
> messages in the other direction arriving out of order.

Yes. Inflight messages from cpu to ioapic was what I was referring to.

thanks,
suresh

  reply	other threads:[~2007-05-18 19:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 23:03 [patch] x86_64, irq: check remote IRR bit before migrating level triggered irq Siddha, Suresh B
2007-05-17 23:58 ` Eric W. Biederman
2007-05-18  0:43   ` Siddha, Suresh B
2007-05-18  0:30 ` Eric W. Biederman
2007-05-18  1:01   ` Siddha, Suresh B
2007-05-18 14:40     ` Eric W. Biederman
2007-05-18 17:30       ` Yinghai Lu
2007-05-18 18:01         ` Eric W. Biederman
2007-05-18 18:09           ` Yinghai Lu
2007-05-18 18:20             ` Eric W. Biederman
2007-05-18 18:07       ` Siddha, Suresh B
2007-05-18 18:28         ` Yinghai Lu
2007-05-18 18:39           ` Siddha, Suresh B
2007-05-18 19:02             ` Eric W. Biederman
2007-05-18 19:18               ` Siddha, Suresh B [this message]
2007-05-31  2:50         ` Eric W. Biederman
2007-05-18 12:00 ` Andi Kleen
2007-05-18 14:19   ` Eric W. Biederman
2007-05-31 11:34 ` [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v2) Eric W. Biederman
2007-05-31 12:01   ` Andi Kleen
2007-05-31 13:29     ` Eric W. Biederman
2007-05-31 20:02       ` Siddha, Suresh B
2007-05-31 13:34   ` Ingo Molnar
2007-05-31 13:50     ` [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v3) Eric W. Biederman
2007-05-31 13:54       ` Ingo Molnar
2007-05-31 20:00       ` Siddha, Suresh B

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=20070518191813.GC28957@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=asit.k.mallick@intel.com \
    --cc=ebiederm@xmission.com \
    --cc=keith.packard@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nanhai.zou@intel.com \
    --cc=yhlu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.