From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 5/8] genirq/irq: introduce msi_doorbell_info
Date: Thu, 28 Apr 2016 08:22:07 +0000 [thread overview]
Message-ID: <1461831730-5575-6-git-send-email-eric.auger@linaro.org> (raw)
In-Reply-To: <1461831730-5575-1-git-send-email-eric.auger@linaro.org>
The purpose is to be able to retrieve the MSI doorbells of an irqchip.
This is now needed since on some platforms those doorbells must be
iommu mapped (in case the MSIs transit through an IOMMU that do not
bypass those transactions).
The assumption is there is a maximum of one doorbell region per cpu.
A doorbell region is characterized by its physical address base, size and
IOMMU protection flag. Those 2 last characteristics are shared among all
doorbells.
irq_chip msi_doorbell_info callback enables to retrieve the doorbells of
the irqchip.
Signed-off-by: Eric Auger <eric.auger@linaro.org>
---
v7 -> v8:
- size and prot now are shared among all doorbells
- doorbells now directly points to a percpu phys_addr_t
v7: creation
---
include/linux/irq.h | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index c4de623..5dbb26d 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -312,6 +312,19 @@ static inline irq_hw_number_t irqd_to_hwirq(struct irq_data *d)
return d->hwirq;
}
+/*
+ * Describe all the MSI doorbell regions for an irqchip.
+ * A single doorbell region per cpu is assumed.
+ * In case a single doorbell is supported for the whole irqchip,
+ * the region is described in as cpu #0's one
+ */
+struct irq_chip_msi_doorbell_info {
+ phys_addr_t __percpu *percpu_doorbells; /* per cpu base address */
+ size_t size; /* size of a each doorbell */
+ int prot; /* iommu protection flag */
+ int nb_doorbells;
+};
+
/**
* struct irq_chip - hardware interrupt chip descriptor
*
@@ -349,6 +362,7 @@ static inline irq_hw_number_t irqd_to_hwirq(struct irq_data *d)
* @irq_get_irqchip_state: return the internal state of an interrupt
* @irq_set_irqchip_state: set the internal state of a interrupt
* @irq_set_vcpu_affinity: optional to target a vCPU in a virtual machine
+ * @msi_doorbell_info: return the MSI doorbell info
* @ipi_send_single: send a single IPI to destination cpus
* @ipi_send_mask: send an IPI to destination cpus in cpumask
* @flags: chip specific flags
@@ -394,7 +408,8 @@ struct irq_chip {
int (*irq_set_irqchip_state)(struct irq_data *data, enum irqchip_irq_state which, bool state);
int (*irq_set_vcpu_affinity)(struct irq_data *data, void *vcpu_info);
-
+ struct irq_chip_msi_doorbell_info *(*msi_doorbell_info)(
+ struct irq_data *data);
void (*ipi_send_single)(struct irq_data *data, unsigned int cpu);
void (*ipi_send_mask)(struct irq_data *data, const struct cpumask *dest);
--
1.9.1
next prev parent reply other threads:[~2016-04-28 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 8:22 [PATCH v8 0/8] KVM PCIe/MSI passthrough on ARM/ARM64: kernel part 2/3: msi changes Eric Auger
2016-04-28 8:22 ` [PATCH v8 1/8] genirq/msi: Add a new MSI_FLAG_IRQ_REMAPPING flag Eric Auger
2016-04-28 8:22 ` [PATCH v8 2/8] irqchip/gic-v3-its: ITS advertises MSI_FLAG_IRQ_REMAPPING Eric Auger
2016-04-28 8:22 ` [PATCH v8 3/8] genirq/msi: export msi_get_domain_info Eric Auger
2016-04-28 8:22 ` [PATCH v8 4/8] genirq/msi: msi_compose wrapper Eric Auger
2016-04-28 8:22 ` Eric Auger [this message]
2016-05-04 12:57 ` [PATCH v8 5/8] genirq/irq: introduce msi_doorbell_info Marc Zyngier
2016-04-28 8:22 ` [PATCH v8 6/8] irqchip/gicv2m: implement msi_doorbell_info callback Eric Auger
2016-05-04 13:02 ` Marc Zyngier
2016-04-28 8:22 ` [PATCH v8 7/8] genirq/msi: map/unmap the MSI doorbells on msi_domain_alloc/free_irqs Eric Auger
2016-05-04 13:21 ` Marc Zyngier
2016-05-04 15:22 ` Eric Auger
2016-04-28 8:22 ` [PATCH v8 8/8] genirq/msi: use the MSI doorbell's IOVA when requested Eric Auger
2016-05-04 13:23 ` Marc Zyngier
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=1461831730-5575-6-git-send-email-eric.auger@linaro.org \
--to=eric.auger@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).