From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/xen: Use xen-specific path for interrupt delivery
Date: Mon, 9 Feb 2009 12:18:56 +0100 [thread overview]
Message-ID: <20090209111856.GB4626@elte.hu> (raw)
In-Reply-To: <498CD755.5030301@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Rather than mapping event channels to vectors and then using the
> vector->irq mapping for interrupt delivery, just cut out the middleman
> and directly map event channels to irqs. This allows for some more
> cleanups in the event handling code.
>
> The following changes since commit 637f52a7cc5b3ae22354b7e45397375a17d626af:
> Jeremy Fitzhardinge (1):
> x86: unify do_IRQ()
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git jsgf/xen/irq
>
> Jeremy Fitzhardinge (5):
> xen: set irq_chip disable
> xen: use our own eventchannel->irq path
> xen: pack all irq-related info together
> xen: remove irq bindcount
> xen: make sure that softirqs get handled at the end of event processing
>
> arch/x86/include/asm/xen/events.h | 6 -
> arch/x86/xen/irq.c | 17 +---
> drivers/xen/events.c | 224 +++++++++++++++++++++++++------------
> 3 files changed, 155 insertions(+), 92 deletions(-)
Ok, never mind my comment on the do_IRQ() detail, this looks good after all,
you just consolidated what is there already in essence.
Pulled into tip/x86/apic [which had dependencies here], thanks Jeremy!
Btw., please remove leftover bits like:
+ //printk("cpu %d handling irq %d\n", smp_processor_id(), info->irq);
Ingo
prev parent reply other threads:[~2009-02-09 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 0:35 Jeremy Fitzhardinge
2009-02-09 11:18 ` Ingo Molnar [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=20090209111856.GB4626@elte.hu \
--to=mingo@elte.hu \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®