From: Ian Campbell <Ian.Campbell@citrix.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [patch 0/4] XEN: Interrupt cleanups
Date: Mon, 7 Feb 2011 21:56:51 +0000 [thread overview]
Message-ID: <1297115811.2959.395.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20110205200108.921707839@linutronix.de>
On Sat, 2011-02-05 at 20:08 +0000, Thomas Gleixner wrote:
> Jeremy,
>
> the following series converts the interrupt chips of XEN to the new
> chip functions and the last patches replace the xen private resume
> hackery.
>
> The first two patches have no dependencies.
>
> The last two need the modification to the generic interrupt layer. I
> could either carry them through the genirq tree with your
> acked-tested-whatever-by or I provide you a branch to pull that change
> from. I need the genirq change local as it conflicts with other patches
> in the pipeline. Either way works fine.
I definitely like IRQF_FORCE_RESUME bits, clearly much better than the
current solution.
I applied the complete series applied on top of current Linus tree (with
fixlet from my reply to 2/4 and a little reject fixup in irq.h from
3/4).
It appears that with all 4 patches applied IPIs aren't getting
resumed/unmasked/something else after a migration.
Adding an irq_enable hook to the relevant irq_chip didn't fix it and I
didn't get a chance to dig any deeper this evening.
I'll look a bit closer tomorrow and get back to you.
Ian.
prev parent reply other threads:[~2011-02-08 9:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 20:08 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
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 [this message]
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=1297115811.2959.395.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--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 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®