From: Julien Grall <julien.grall@linaro.org>
To: xen-devel@lists.xenproject.org
Cc: stefano.stabellini@citrix.com,
Julien Grall <julien.grall@linaro.org>,
tim@xen.org, ian.campbell@citrix.com
Subject: [PATCH v5 0/6] xen/arm: Interrupt management reworking
Date: Fri, 2 May 2014 16:52:04 +0100 [thread overview]
Message-ID: <1399045930-17364-1-git-send-email-julien.grall@linaro.org> (raw)
Hello,
This is the fifth version of this series to rework interrupt management for
ARM.
This patchset is smaller than the previous version as Ian Campbell has already
pushed most of the patches.
Major changes in v6:
- Introduce boot_cpu macro
- Fix wrong test condition in exynos4210 drivers
Every patches are acked except:
- #1: new patch
- #6: Only acked for non-ARM part
For all changes see in each patch.
This series is a dependency for the ARM SMMU drivers.
A working tree can be found here:
git://xenbits.xen.org/people/julieng/xen-unstable.git branch interrupt-mgmt-v5
Sincerely yours,
Julien Grall (6):
xen: Add convenient macro boot_cpu
xen/arm: IRQ: Store IRQ type in arch_irq_desc
xen/arm: IRQ: Replace {request,setup}_dt_irq by {request,setup}_irq
xen: IRQ: Add dev_id parameter to release_irq
xen/arm: IRQ: extend {request,setup}_irq to take an irqflags in
parameter
xen/arm: IRQ: Handle multiple action per IRQ
xen/arch/arm/gic.c | 36 +++---
xen/arch/arm/irq.c | 189 ++++++++++++++++++++++++------
xen/arch/arm/setup.c | 3 +-
xen/arch/arm/time.c | 30 ++---
xen/arch/x86/hpet.c | 2 +-
xen/arch/x86/i8259.c | 2 +-
xen/arch/x86/irq.c | 11 +-
xen/arch/x86/time.c | 2 +-
xen/drivers/char/exynos4210-uart.c | 15 +--
xen/drivers/char/ns16550.c | 20 +---
xen/drivers/char/omap-uart.c | 15 +--
xen/drivers/char/pl011.c | 18 +--
xen/drivers/passthrough/amd/iommu_init.c | 2 +-
xen/drivers/passthrough/vtd/iommu.c | 2 +-
xen/include/asm-arm/config.h | 2 +
xen/include/asm-arm/gic.h | 5 +-
xen/include/asm-arm/irq.h | 8 +-
xen/include/xen/irq.h | 11 +-
xen/include/xen/percpu.h | 3 +
19 files changed, 252 insertions(+), 124 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-05-02 15:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:52 Julien Grall [this message]
2014-05-02 15:52 ` [PATCH v5 1/6] xen: Add convenient macro boot_cpu Julien Grall
2014-05-02 15:57 ` Andrew Cooper
2014-05-06 15:54 ` Julien Grall
2014-05-08 9:57 ` Ian Campbell
2014-05-12 12:36 ` Julien Grall
2014-05-08 9:55 ` Ian Campbell
2014-05-08 10:00 ` Jan Beulich
2014-05-08 10:19 ` Ian Campbell
2014-05-05 7:59 ` Jan Beulich
2014-05-06 15:58 ` Julien Grall
2014-05-06 16:04 ` Jan Beulich
2014-05-06 16:09 ` Andrew Cooper
2014-05-02 15:52 ` [PATCH v5 2/6] xen/arm: IRQ: Store IRQ type in arch_irq_desc Julien Grall
2014-05-08 10:03 ` Ian Campbell
2014-05-12 12:34 ` Julien Grall
2014-05-02 15:52 ` [PATCH v5 3/6] xen/arm: IRQ: Replace {request, setup}_dt_irq by {request, setup}_irq Julien Grall
2014-05-02 15:52 ` [PATCH v5 4/6] xen: IRQ: Add dev_id parameter to release_irq Julien Grall
2014-05-02 15:52 ` [PATCH v5 5/6] xen/arm: IRQ: extend {request, setup}_irq to take an irqflags in parameter Julien Grall
2014-05-02 15:52 ` [PATCH v5 6/6] xen/arm: IRQ: Handle multiple action per IRQ Julien Grall
2014-05-08 10:04 ` 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=1399045930-17364-1-git-send-email-julien.grall@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).