All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [patch 0/4] XEN: Interrupt cleanups
Date: Mon, 07 Feb 2011 13:57:58 -0800	[thread overview]
Message-ID: <4D506AE6.6080900@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1102072231220.31804@localhost6.localdomain6>

On 02/07/2011 01:33 PM, Thomas Gleixner wrote:
> Ok. The irq_chip conversion is mostly mechanical, but I'm really
> concerned about that IRQ_SUSPENDED hackery. It'd be nice if you
> resp. Ian could give that a test ride. That would allow me to cleanup
> stuff in the core code.

Ian notes: "tglx's 4 patch interrupt cleanup series on LKML causes some
oddities on PV migration. Will dig further tomorrow..."

So it looks like there's still something amiss.

    J

  reply	other threads:[~2011-02-07 21:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 20:08 [patch 0/4] XEN: Interrupt cleanups Thomas Gleixner
2011-02-05 20:08 ` [patch 1/4] xen: Remove stale irq_chip.end Thomas Gleixner
2011-02-05 20:08 ` [patch 2/4] xen: Switch to new irq_chip functions Thomas Gleixner
2011-02-07 11:08   ` Ian Campbell
2011-02-07 11:30     ` Thomas Gleixner
2011-02-05 20:08 ` [patch 3/4] genirq: Add IRQF_FORCE_RESUME Thomas Gleixner
2011-02-05 20:08 ` [patch 4/4] xen: Use IRQF_FORCE_RESUME Thomas Gleixner
2011-02-07 21:28 ` [patch 0/4] XEN: Interrupt cleanups Jeremy Fitzhardinge
2011-02-07 21:33   ` Thomas Gleixner
2011-02-07 21:57     ` Jeremy Fitzhardinge [this message]
2011-02-08 14:03       ` Ian Campbell
2011-02-08 14:55         ` Thomas Gleixner
2011-02-08 15:05           ` Ian Campbell
2011-02-08 15:39             ` Thomas Gleixner
2011-02-08 16:20               ` Konrad Rzeszutek Wilk
2011-02-08 16:31                 ` Ian Campbell
2011-02-08 17:33                 ` Thomas Gleixner
2011-02-08 18:39                   ` Konrad Rzeszutek Wilk
2011-02-08 19:05                     ` Thomas Gleixner
2011-02-09  9:27                 ` Ian Campbell
2011-02-09  9:46                   ` Thomas Gleixner
2011-02-09  9:48                     ` Thomas Gleixner
2011-02-09 10:16                       ` Ian Campbell
2011-02-09  9:56                     ` Ian Campbell
2011-02-08 16:24               ` Konrad Rzeszutek Wilk
2011-02-08 17:38                 ` Thomas Gleixner
2011-02-08 16:26               ` Ian Campbell
2011-02-07 21:56 ` Ian Campbell

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=4D506AE6.6080900@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.