PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
Subsystems (5)
v10 cover PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
From: Jake Oshins <[email protected]>
This version of the patch series removes warning when compiling x86 32-bit while still making it build cleanly for x64.
First, export functions that allow correlating Hyper-V virtual processors and Linux cpus, along with the means for invoking a hypercall that targets interrupts at chosen vectors on specific cpus.
Second, mark various parts of IRQ domain related code as exported, so that this PCI front-end can implement an IRQ domain as part of a module. (The alternative would be to pull all tyhis into the kernel, which would pull in a lot of other Hyper-V related code, as this IRQ domain depends on vmbus.ko.)
Third, modify PCI so that new root PCI buses can be marked with an associated fwnode_handle, and so that root PCI buses can look up their associated IRQ domain by that handle.
Fourth, introduce a new driver, hv_pcifront, which exposes root PCI buses in a Hyper-V VM. These root PCI buses expose real PCIe device, or PCI Virtual Functions.
Jake Oshins (7):
drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
proc num
drivers:hv: Export hv_do_hypercall()
PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
PCI: Add fwnode_handle to pci_sysdata
PCI: irqdomain: Look up IRQ domain by fwnode_handle drivers:hv: Define the channel type of Hyper-V PCI Express
pass-through
PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
MAINTAINERS | 1 + arch/x86/include/asm/msi.h | 6 + arch/x86/include/asm/pci.h | 15 + arch/x86/kernel/apic/msi.c | 8 +- arch/x86/kernel/apic/vector.c | 2 + drivers/hv/hv.c | 20 +- drivers/hv/hyperv_vmbus.h | 2 +- drivers/hv/vmbus_drv.c | 17 + drivers/pci/Kconfig | 7 + drivers/pci/host/Makefile | 1 + drivers/pci/host/hv_pcifront.c | 2249 ++++++++++++++++++++++++++++++++++++++++ drivers/pci/msi.c | 4 + drivers/pci/probe.c | 15 + include/linux/hyperv.h | 14 + include/linux/pci.h | 4 + kernel/irq/chip.c | 1 + kernel/irq/irqdomain.c | 4 + 17 files changed, 2356 insertions(+), 14 deletions(-) create mode 100644 drivers/pci/host/hv_pcifront.c
Signature · 1 line
1.9.1
PATCH v10 1/7 drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num
From: Jake Oshins <[email protected]>
This patch exposes the mapping between Linux CPU number and Hyper-V virtual processor number. This is necessary because the hypervisor needs to know which virtual processor to target when making a mapping in the Interrupt Redirection Table in the I/O MMU.
--- drivers/hv/vmbus_drv.c | 17 +++++++++++++++++ include/linux/hyperv.h | 2 ++ 2 files changed, 19 insertions(+)
drivers/hv/vmbus_drv.c +17 -0
@@ -1191,6 +1191,23 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj, }EXPORT_SYMBOL_GPL (vmbus_allocate_mmio); +/** +* vmbus_cpu_number_to_vp_number() - Map CPU to VP. +* @cpu_number: CPU number in Linux terms +* +* This function returns the mapping between the Linux processor +* number and the hypervisor's virtual processor number, useful +* in making hypercalls and such that talk about specific +* processors. +* +* Return: Virtual processor number in Hyper-V terms +*/ +int vmbus_cpu_number_to_vp_number (int cpu_number) +{ +return hv_context.vp_index[cpu_number]; +} +EXPORT_SYMBOL_GPL (vmbus_cpu_number_to_vp_number); +static int vmbus_acpi_add (struct acpi_device *device) {acpi_status result;
include/linux/hyperv.h +2 -0
@@ -983,6 +983,8 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj, resource_size_t size, resource_size_t align, bool fb_overlap_ok); +int vmbus_cpu_number_to_vp_number (int cpu_number); +/** * VMBUS_DEVICE - macro used to describe a specific hyperv vmbus device *
Signature · 1 line
1.9.1
PATCH v10 2/7 drivers:hv: Export hv_do_hypercall()
In reply to [email protected]From: Jake Oshins <[email protected]>
This patch exposes the function that hv_vmbus.ko uses to make hypercalls. This is necessary for retargeting an interrupt when it is given a new affinity and vector.
--- drivers/hv/hv.c | 20 ++++++++++---------- drivers/hv/hyperv_vmbus.h | 2 +- include/linux/hyperv.h | 1 + 3 files changed, 12 insertions(+), 11 deletions(-)
drivers/hv/hv.c +10 -10
@@ -89,9 +89,9 @@ static int query_hypervisor_info(void) }/* -* do_hypercall- Invoke the specified hypercall +* hv_do_hypercall- Invoke the specified hypercall */ -static u64 do_hypercall (u64 control,void *input,void *output) +u64 hv_do_hypercall (u64 control,void *input,void *output) {u64 input_address = (input) ?virt_to_phys (input) :0 ;u64 output_address = (output) ?virt_to_phys (output) :0 ;
@@ -132,6 +132,7 @@ static u64 do_hypercall(u64 control, void *input, void *output)return hv_status_lo | ((u64 )hv_status_hi <<32 );#endif /* !x86_64 */ } +EXPORT_SYMBOL_GPL (hv_do_hypercall);#ifdef CONFIG_X86_64 static cycle_t read_hv_clock_tsc (struct clocksource *arg)
@@ -315,7 +316,7 @@ int hv_post_message(union hv_connection_id connection_id, {struct hv_input_post_message *aligned_msg; -u16 status; +u64 status;if (payload_size >HV_MESSAGE_PAYLOAD_BYTE_COUNT )return -EMSGSIZE ;
@@ -329,11 +330,10 @@ int hv_post_message(union hv_connection_id connection_id, aligned_msg->payload_size = payload_size;memcpy ((void *)aligned_msg->payload, payload, payload_size); - status =do_hypercall (HVCALL_POST_MESSAGE , aligned_msg,NULL ) - &0xFFFF ; + status =hv_do_hypercall (HVCALL_POST_MESSAGE , aligned_msg,NULL );put_cpu (); -return status; +return status &0xFFFF ; }
@@ -343,13 +343,13 @@ int hv_post_message(union hv_connection_id connection_id,* * This involves a hypercall. */ -u16 hv_signal_event (void *con_id) +int hv_signal_event (void *con_id) { -u16 status; +u64 status; - status = (do_hypercall (HVCALL_SIGNAL_EVENT , con_id,NULL ) &0xFFFF ); + status =hv_do_hypercall (HVCALL_SIGNAL_EVENT , con_id,NULL ); -return status; +return status &0xFFFF ; } static int hv_ce_set_next_event(unsigned long delta,
drivers/hv/hyperv_vmbus.h +1 -1
@@ -582,7 +582,7 @@ extern int hv_post_message(union hv_connection_id connection_id,enum hv_message_type message_type, void *payload, size_t payload_size); -extern u16 hv_signal_event (void *con_id); +extern int hv_signal_event (void *con_id);extern int hv_synic_alloc (void );
include/linux/hyperv.h +1 -0
@@ -984,6 +984,7 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj, bool fb_overlap_ok);int vmbus_cpu_number_to_vp_number (int cpu_number); +u64 hv_do_hypercall (u64 control,void *input,void *output);/** * VMBUS_DEVICE - macro used to describe a specific hyperv vmbus device
Signature · 1 line
1.9.1
PATCH v10 3/7 PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
In reply to [email protected]From: Jake Oshins <[email protected]>
The Linux kernel already has the concpet of IRQ domain, wherein a component can expose a set of IRQs which are managed by a particular interrupt controller chip or other subsystem. The PCI driver exposes the notion of an IRQ domain for Message-Signaled Interrupts (MSI) from PCI Express devices. This patch exposes the functions which are necessary for making an MSI IRQ domain within a module.
--- arch/x86/include/asm/msi.h | 6 ++++++ arch/x86/kernel/apic/msi.c | 8 +++++--- arch/x86/kernel/apic/vector.c | 2 ++ drivers/pci/msi.c | 4 ++++ kernel/irq/chip.c | 1 + kernel/irq/irqdomain.c | 4 ++++ 6 files changed, 22 insertions(+), 3 deletions(-)
arch/x86/include/asm/msi.h +6 -0
@@ -1,7 +1,13 @@#ifndef _ASM_X86_MSI_H#define _ASM_X86_MSI_H#include <asm/hw_irq.h> +#include <asm/irqdomain.h> typedef struct irq_alloc_info msi_alloc_info_t ; +int pci_msi_prepare (struct irq_domain *domain,struct device *dev,int nvec, +msi_alloc_info_t *arg); + +void pci_msi_set_desc (msi_alloc_info_t *arg,struct msi_desc *desc); +#endif /* _ASM_X86_MSI_H */
arch/x86/kernel/apic/msi.c +5 -3
@@ -96,8 +96,8 @@ static irq_hw_number_t pci_msi_get_hwirq(struct msi_domain_info *info,return arg->msi_hwirq; } -static int pci_msi_prepare (struct irq_domain *domain,struct device *dev, -int nvec,msi_alloc_info_t *arg) +int pci_msi_prepare (struct irq_domain *domain,struct device *dev,int nvec, +msi_alloc_info_t *arg) {struct pci_dev *pdev =to_pci_dev (dev);struct msi_desc *desc =first_pci_msi_entry (pdev);
@@ -113,11 +113,13 @@ static int pci_msi_prepare(struct irq_domain *domain, struct device *dev,return 0 ; } +EXPORT_SYMBOL_GPL (pci_msi_prepare); -static void pci_msi_set_desc (msi_alloc_info_t *arg,struct msi_desc *desc) +void pci_msi_set_desc (msi_alloc_info_t *arg,struct msi_desc *desc) { arg->msi_hwirq =pci_msi_domain_calc_hwirq (arg->msi_dev, desc); } +EXPORT_SYMBOL_GPL (pci_msi_set_desc);static struct msi_domain_ops pci_msi_domain_ops = { .get_hwirq = pci_msi_get_hwirq,
arch/x86/kernel/apic/vector.c +2 -0
@@ -29,6 +29,7 @@ struct apic_chip_data { };struct irq_domain *x86_vector_domain; +EXPORT_SYMBOL_GPL (x86_vector_domain);static DEFINE_RAW_SPINLOCK (vector_lock);static cpumask_var_t vector_cpumask;static struct irq_chip lapic_controller;
@@ -66,6 +67,7 @@ struct irq_cfg *irqd_cfg(struct irq_data *irq_data)return data ? &data->cfg :NULL ; } +EXPORT_SYMBOL_GPL (irqd_cfg);struct irq_cfg *irq_cfg (unsigned int irq) {
drivers/pci/msi.c +4 -0
@@ -257,6 +257,7 @@ void pci_msi_mask_irq(struct irq_data *data) {msi_set_mask_bit (data,1 ); } +EXPORT_SYMBOL_GPL (pci_msi_mask_irq);/** * pci_msi_unmask_irq - Generic irq chip callback to unmask PCI/MSI interrupts
@@ -266,6 +267,7 @@ void pci_msi_unmask_irq(struct irq_data *data) {msi_set_mask_bit (data,0 ); } +EXPORT_SYMBOL_GPL (pci_msi_unmask_irq);void default_restore_msi_irqs (struct pci_dev *dev) {
@@ -1126,6 +1128,7 @@ struct pci_dev *msi_desc_to_pci_dev(struct msi_desc *desc) {return to_pci_dev (desc->dev); } +EXPORT_SYMBOL (msi_desc_to_pci_dev);void *msi_desc_to_pci_sysdata (struct msi_desc *desc) {
@@ -1285,6 +1288,7 @@ struct irq_domain *pci_msi_create_irq_domain(struct fwnode_handle *fwnode, domain->bus_token =DOMAIN_BUS_PCI_MSI ;return domain; } +EXPORT_SYMBOL_GPL (pci_msi_create_irq_domain);/** * pci_msi_domain_alloc_irqs - Allocate interrupts for @dev in @domain
kernel/irq/chip.c +1 -0
@@ -950,6 +950,7 @@ void irq_chip_ack_parent(struct irq_data *data) data = data->parent_data; data->chip->irq_ack (data); } +EXPORT_SYMBOL_GPL (irq_chip_ack_parent);/** * irq_chip_mask_parent - Mask the parent interrupt
kernel/irq/irqdomain.c +4 -0
@@ -60,6 +60,7 @@ struct fwnode_handle *irq_domain_alloc_fwnode(void *data) fwid->fwnode.type =FWNODE_IRQCHIP ;return &fwid->fwnode; } +EXPORT_SYMBOL_GPL (irq_domain_alloc_fwnode);/** * irq_domain_free_fwnode - Free a non-OF-backed fwnode_handle
@@ -77,6 +78,7 @@ void irq_domain_free_fwnode(struct fwnode_handle *fwnode)kfree (fwid->name);kfree (fwid); } +EXPORT_SYMBOL_GPL (irq_domain_free_fwnode);/** * __irq_domain_add() - Allocate a new irq_domain data structure
@@ -1013,6 +1015,7 @@ struct irq_data *irq_domain_get_irq_data(struct irq_domain *domain,return NULL ; } +EXPORT_SYMBOL_GPL (irq_domain_get_irq_data);/** * irq_domain_set_hwirq_and_chip - Set hwirq and irqchip of @virq at @domain
@@ -1343,6 +1346,7 @@ struct irq_data *irq_domain_get_irq_data(struct irq_domain *domain,return (irq_data && irq_data->domain == domain) ? irq_data :NULL ; } +EXPORT_SYMBOL_GPL (irq_domain_get_irq_data);/** * irq_domain_set_info - Set the complete data for a @virq in @domain
Signature · 1 line
1.9.1
Re: [PATCH v10 3/7] PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
Quoted 10 lines · On 10/12/15 17:52, [email protected] wrote:
From: Jake Oshins <[email protected]>
The Linux kernel already has the concpet of IRQ domain, wherein a component can expose a set of IRQs which are managed by a particular interrupt controller chip or other subsystem. The PCI driver exposes the notion of an IRQ domain for Message-Signaled Interrupts (MSI) from PCI Express devices. This patch exposes the functions which are necessary for making an MSI IRQ domain within a module.
Signed-off-by Jake Oshins <[email protected]>
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
tip-bot for Jake Oshins
merge bot[tip:irq/core] genirq/msi: Export functions to allow MSI domains in modules
In reply to [email protected]genirq/msi: Export functions to allow MSI domains in modules
Commit-ID: a4289dc2ec3a5821076a78ee9678909b4eff297e Gitweb: http://git.kernel.org/tip/a4289dc2ec3a5821076a78ee9678909b4eff297e Author: Jake Oshins <[email protected]> AuthorDate: Thu, 10 Dec 2015 17:52:59 +0000 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 20 Dec 2015 12:26:52 +0100
genirq/msi: Export functions to allow MSI domains in modules
The Linux kernel already has the concept of IRQ domain, wherein a component can expose a set of IRQs which are managed by a particular interrupt controller chip or other subsystem. The PCI driver exposes the notion of an IRQ domain for Message-Signaled Interrupts (MSI) from PCI Express devices. This patch exposes the functions which are necessary for creating a MSI IRQ domain within a module.
[ tglx: Split it into x86 and core irq parts ]
--- drivers/pci/msi.c | 4 ++++ kernel/irq/chip.c | 1 + kernel/irq/irqdomain.c | 4 ++++ 3 files changed, 9 insertions(+)
drivers/pci/msi.c +4 -0
@@ -257,6 +257,7 @@ void pci_msi_mask_irq(struct irq_data *data) {msi_set_mask_bit (data,1 ); } +EXPORT_SYMBOL_GPL (pci_msi_mask_irq);/** * pci_msi_unmask_irq - Generic irq chip callback to unmask PCI/MSI interrupts
@@ -266,6 +267,7 @@ void pci_msi_unmask_irq(struct irq_data *data) {msi_set_mask_bit (data,0 ); } +EXPORT_SYMBOL_GPL (pci_msi_unmask_irq);void default_restore_msi_irqs (struct pci_dev *dev) {
@@ -1126,6 +1128,7 @@ struct pci_dev *msi_desc_to_pci_dev(struct msi_desc *desc) {return to_pci_dev (desc->dev); } +EXPORT_SYMBOL (msi_desc_to_pci_dev);void *msi_desc_to_pci_sysdata (struct msi_desc *desc) {
@@ -1285,6 +1288,7 @@ struct irq_domain *pci_msi_create_irq_domain(struct fwnode_handle *fwnode, domain->bus_token =DOMAIN_BUS_PCI_MSI ;return domain; } +EXPORT_SYMBOL_GPL (pci_msi_create_irq_domain);/** * pci_msi_domain_alloc_irqs - Allocate interrupts for @dev in @domain
kernel/irq/chip.c +1 -0
@@ -950,6 +950,7 @@ void irq_chip_ack_parent(struct irq_data *data) data = data->parent_data; data->chip->irq_ack (data); } +EXPORT_SYMBOL_GPL (irq_chip_ack_parent);/** * irq_chip_mask_parent - Mask the parent interrupt
kernel/irq/irqdomain.c +4 -0
@@ -60,6 +60,7 @@ struct fwnode_handle *irq_domain_alloc_fwnode(void *data) fwid->fwnode.type =FWNODE_IRQCHIP ;return &fwid->fwnode; } +EXPORT_SYMBOL_GPL (irq_domain_alloc_fwnode);/** * irq_domain_free_fwnode - Free a non-OF-backed fwnode_handle
@@ -77,6 +78,7 @@ void irq_domain_free_fwnode(struct fwnode_handle *fwnode)kfree (fwid->name);kfree (fwid); } +EXPORT_SYMBOL_GPL (irq_domain_free_fwnode);/** * __irq_domain_add() - Allocate a new irq_domain data structure
@@ -1013,6 +1015,7 @@ struct irq_data *irq_domain_get_irq_data(struct irq_domain *domain,return NULL ; } +EXPORT_SYMBOL_GPL (irq_domain_get_irq_data);/** * irq_domain_set_hwirq_and_chip - Set hwirq and irqchip of @virq at @domain
@@ -1343,6 +1346,7 @@ struct irq_data *irq_domain_get_irq_data(struct irq_domain *domain,return (irq_data && irq_data->domain == domain) ? irq_data :NULL ; } +EXPORT_SYMBOL_GPL (irq_domain_get_irq_data);/** * irq_domain_set_info - Set the complete data for a @virq in @domain
tip-bot for Jake Oshins
merge bot[tip:x86/apic] x86/irq: Export functions to allow MSI domains in modules
In reply to [email protected]x86/irq: Export functions to allow MSI domains in modules
Commit-ID: c8f3e518d3444ee9200a4987421fcee60f768f11 Gitweb: http://git.kernel.org/tip/c8f3e518d3444ee9200a4987421fcee60f768f11 Author: Jake Oshins <[email protected]> AuthorDate: Thu, 10 Dec 2015 17:52:59 +0000 Committer: Thomas Gleixner <[email protected]> CommitDate: Sun, 20 Dec 2015 12:40:49 +0100
x86/irq: Export functions to allow MSI domains in modules
The Linux kernel already has the concept of IRQ domain, wherein a component can expose a set of IRQs which are managed by a particular interrupt controller chip or other subsystem. The PCI driver exposes the notion of an IRQ domain for Message-Signaled Interrupts (MSI) from PCI Express devices. This patch exposes the functions which are necessary for creating a MSI IRQ domain within a module.
[ tglx: Split it into x86 and core irq parts ]
--- arch/x86/include/asm/msi.h | 6 ++++++ arch/x86/kernel/apic/msi.c | 8 +++++--- arch/x86/kernel/apic/vector.c | 2 ++ 3 files changed, 13 insertions(+), 3 deletions(-)
arch/x86/include/asm/msi.h +6 -0
@@ -1,7 +1,13 @@#ifndef _ASM_X86_MSI_H#define _ASM_X86_MSI_H#include <asm/hw_irq.h> +#include <asm/irqdomain.h> typedef struct irq_alloc_info msi_alloc_info_t ; +int pci_msi_prepare (struct irq_domain *domain,struct device *dev,int nvec, +msi_alloc_info_t *arg); + +void pci_msi_set_desc (msi_alloc_info_t *arg,struct msi_desc *desc); +#endif /* _ASM_X86_MSI_H */
arch/x86/kernel/apic/msi.c +5 -3
@@ -96,8 +96,8 @@ static irq_hw_number_t pci_msi_get_hwirq(struct msi_domain_info *info,return arg->msi_hwirq; } -static int pci_msi_prepare (struct irq_domain *domain,struct device *dev, -int nvec,msi_alloc_info_t *arg) +int pci_msi_prepare (struct irq_domain *domain,struct device *dev,int nvec, +msi_alloc_info_t *arg) {struct pci_dev *pdev =to_pci_dev (dev);struct msi_desc *desc =first_pci_msi_entry (pdev);
@@ -113,11 +113,13 @@ static int pci_msi_prepare(struct irq_domain *domain, struct device *dev,return 0 ; } +EXPORT_SYMBOL_GPL (pci_msi_prepare); -static void pci_msi_set_desc (msi_alloc_info_t *arg,struct msi_desc *desc) +void pci_msi_set_desc (msi_alloc_info_t *arg,struct msi_desc *desc) { arg->msi_hwirq =pci_msi_domain_calc_hwirq (arg->msi_dev, desc); } +EXPORT_SYMBOL_GPL (pci_msi_set_desc);static struct msi_domain_ops pci_msi_domain_ops = { .get_hwirq = pci_msi_get_hwirq,
arch/x86/kernel/apic/vector.c +2 -0
@@ -29,6 +29,7 @@ struct apic_chip_data { };struct irq_domain *x86_vector_domain; +EXPORT_SYMBOL_GPL (x86_vector_domain);static DEFINE_RAW_SPINLOCK (vector_lock);static cpumask_var_t vector_cpumask;static struct irq_chip lapic_controller;
@@ -66,6 +67,7 @@ struct irq_cfg *irqd_cfg(struct irq_data *irq_data)return data ? &data->cfg :NULL ; } +EXPORT_SYMBOL_GPL (irqd_cfg);struct irq_cfg *irq_cfg (unsigned int irq) {
PATCH v10 4/7 PCI: Add fwnode_handle to pci_sysdata
In reply to [email protected]From: Jake Oshins <[email protected]>
This patch adds an fwnode_handle to struct pci_sysdata, which is used by the next patch in the series when trying to locate an IRQ domain associated with a root PCI bus.
--- arch/x86/include/asm/pci.h | 15 +++++++++++++++ drivers/pci/probe.c | 1 + include/linux/pci.h | 4 ++++ 3 files changed, 20 insertions(+)
arch/x86/include/asm/pci.h +15 -0
@@ -20,6 +20,9 @@ struct pci_sysdata {#ifdef CONFIG_X86_64 void *iommu;/* IOMMU private data */ #endif +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN +void *fwnode;/* IRQ domain for MSI assignment */ +#endif };extern int pci_routeirq;
@@ -32,6 +35,7 @@ extern int noioapicreroute;static inline int pci_domain_nr (struct pci_bus *bus) {struct pci_sysdata *sd = bus->sysdata; +return sd->domain; }
@@ -41,6 +45,17 @@ static inline int pci_proc_domain(struct pci_bus *bus) }#endif +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN +static inline void *_pci_root_bus_fwnode (struct pci_bus *bus) +{ +struct pci_sysdata *sd = bus->sysdata; + +return sd->fwnode; +} + +#define pci_root_bus_fwnode _pci_root_bus_fwnode +#endif +/* Can be used to override the logic in pci_scan_bus for skipping already-configured bus numbers - to be used for buggy BIOSes or architectures with incomplete PCI setup by the loader */
drivers/pci/probe.c +1 -0
@@ -15,6 +15,7 @@#include <linux/pci-aspm.h> #include <linux/aer.h> #include <linux/acpi.h> +#include <linux/irqdomain.h> #include <asm-generic/pci-bridge.h> #include "pci.h"
include/linux/pci.h +4 -0
@@ -1517,6 +1517,10 @@ static inline int pci_get_new_domain_nr(void) { return -ENOSYS; }#include <asm/pci.h> +#ifndef pci_root_bus_fwnode +#define pci_root_bus_fwnode (bus) ((void)(bus), NULL) +#endif +/* these helpers provide future and backwards compatibility * for accessing popular PCI BAR info */ #define pci_resource_start (dev, bar) ((dev)->resource[(bar)].start)
Signature · 1 line
1.9.1
Re: [PATCH v10 4/7] PCI: Add fwnode_handle to pci_sysdata
Quoted 58 lines · On 10/12/15 17:53, [email protected] wrote:
From: Jake Oshins <[email protected]>
This patch adds an
fwnode_handleto structpci_sysdata, which is used by the next patch in the series when trying to locate an IRQ domain associated with a root PCI bus.Signed-off-by Jake Oshins <[email protected]>--- arch/x86/include/asm/pci.h | 15 +++++++++++++++ drivers/pci/probe.c | 1 + include/linux/pci.h | 4 ++++ 3 files changed, 20 insertions(+)arch/x86/include/asm/pci.h +15
-0@@ -20,6 +20,9 @@ struct pci_sysdata {#ifdef CONFIG_X86_64 void *iommu;/* IOMMU private data */ #endif +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN +void *fwnode;/* IRQ domain for MSI assignment */ +#endif };extern int pci_routeirq;@@ -32,6 +35,7 @@ extern int noioapicreroute;static inline int pci_domain_nr (struct pci_bus *bus) {struct pci_sysdata *sd = bus->sysdata; +return sd->domain; }@@ -41,6 +45,17 @@ static inline int pci_proc_domain(struct pci_bus *bus) }#endif +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN +static inline void *_pci_root_bus_fwnode (struct pci_bus *bus) +{ +struct pci_sysdata *sd = bus->sysdata; + +return sd->fwnode; +} + +#define pci_root_bus_fwnode _pci_root_bus_fwnode +#endif +/* Can be used to override the logic in pci_scan_bus for skipping already-configured bus numbers - to be used for buggy BIOSes or architectures with incomplete PCI setup by the loader */ drivers/pci/probe.c +0
-0
drivers/pci/probe.c line 18
Quoted 4 lines
drivers/pci/probe.c +1
-0@@ -15,6 +15,7 @@#include <linux/pci-aspm.h> #include <linux/aer.h> #include <linux/acpi.h> +#include <linux/irqdomain.h>
Nit: this should be with patch 5, but that doesn't hurt. I don't think you need to respin the series for this.
Quoted 9 lines
drivers/pci/probe.c +0
-0#include <asm-generic/pci-bridge.h> #include "pci.h" include/linux/pci.h +0
-0
include/linux/pci.h static inline int pci_get_new_domain_nr(void) { return -ENOSYS; } · line 1526
Quoted 10 lines
include/linux/pci.h +4
-0@@ -1517,6 +1517,10 @@ static inline int pci_get_new_domain_nr(void) { return -ENOSYS; }#include <asm/pci.h> +#ifndef pci_root_bus_fwnode +#define pci_root_bus_fwnode (bus) ((void)(bus), NULL) +#endif +/* these helpers provide future and backwards compatibility * for accessing popular PCI BAR info */ #define pci_resource_start (dev, bar) ((dev)->resource[(bar)].start)
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
PATCH v10 5/7 PCI: irqdomain: Look up IRQ domain by fwnode_handle
In reply to [email protected]From: Jake Oshins <[email protected]>
This patch adds a second way of finding an IRQ domain associated with a root PCI bus. After looking to see if one can be found through the OF tree, it attempts to look up the IRQ domain through an fwnode_handle stored in the pci_sysdata struct.
--- drivers/pci/probe.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
drivers/pci/probe.c +14 -0
@@ -674,6 +674,20 @@ static struct irq_domain *pci_host_bridge_msi_domain(struct pci_bus *bus)*/ d =pci_host_bridge_of_msi_domain (bus); +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN +/* +* If no IRQ domain was found via the OF tree, try looking it up +* directly through the fwnode_handle. +*/ +if (!d) { +struct fwnode_handle *fwnode =pci_root_bus_fwnode (bus); + +if (fwnode) + d =irq_find_matching_fwnode (fwnode, +DOMAIN_BUS_PCI_MSI ); + } +#endif +return d; }
Signature · 1 line
1.9.1
Re: [PATCH v10 5/7] PCI: irqdomain: Look up IRQ domain by fwnode_handle
Quoted 28 lines · On 10/12/15 17:53, [email protected] wrote:
From: Jake Oshins <[email protected]>
This patch adds a second way of finding an IRQ domain associated with a root PCI bus. After looking to see if one can be found through the OF tree, it attempts to look up the IRQ domain through an
fwnode_handlestored in thepci_sysdatastruct.Signed-off-by Jake Oshins <[email protected]>--- drivers/pci/probe.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)drivers/pci/probe.c +7
-0@@ -674,6 +674,20 @@ static struct irq_domain *pci_host_bridge_msi_domain(struct pci_bus *bus)*/ d =pci_host_bridge_of_msi_domain (bus); +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN +/* +* If no IRQ domain was found via the OF tree, try looking it up +* directly through the fwnode_handle. +*/ +if (!d) { +struct fwnode_handle *fwnode =pci_root_bus_fwnode (bus);
drivers/pci/probe.c static struct irq_domain *pci_host_bridge_msi_domain(struct pci_bus *bus) · line 693
Quoted 10 lines
drivers/pci/probe.c +7
-0+ +if (fwnode) + d =irq_find_matching_fwnode (fwnode, + DOMAIN_BUS_PCI_MSI); + } +#endif +return d; }
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
PATCH v10 6/7 drivers:hv: Define the channel type of Hyper-V PCI Express pass-through
In reply to [email protected]From: Jake Oshins <[email protected]>
This defines the channel type for PCI front-ends in Hyper-V VMs.
--- include/linux/hyperv.h | 11 +++++++++++ 1 file changed, 11 insertions(+)
include/linux/hyperv.h +11 -0
@@ -1141,6 +1141,17 @@ u64 hv_do_hypercall(u64 control, void *input, void *output); }/* +* PCI Express Pass Through +* {44C4F61D-4444-4400-9D52-802E27EDE19F} +*/ + +#define HV_PCIE_GUID \ + .guid = { \ + 0x1D, 0xF6, 0xC4, 0x44, 0x44, 0x44, 0x00, 0x44, \ + 0x9D, 0x52, 0x80, 0x2E, 0x27, 0xED, 0xE1, 0x9F \ + } + +/* * Common header for Hyper-V ICs */
Signature · 1 line
1.9.1
PATCH v10 7/7 PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
In reply to [email protected]From: Jake Oshins <[email protected]>
This patch introduces a new driver which exposes a root PCI bus whenever a PCI Express device is passed through to a guest VM under Hyper-V. The device can be single- or multi-function. The interrupts for the devices are managed by an IRQ domain, implemented within the driver.
--- MAINTAINERS | 1 + drivers/pci/Kconfig | 7 + drivers/pci/host/Makefile | 1 + drivers/pci/host/hv_pcifront.c | 2249 ++++++++++++++++++++++++++++++++++++++++ 4 files changed, 2258 insertions(+) create mode 100644 drivers/pci/host/hv_pcifront.c
MAINTAINERS +1 -0
@@ -5115,6 +5115,7 @@ F: arch/x86/kernel/cpu/mshyperv.c F: drivers/hid/hid-hyperv.c F: drivers/hv/ F: drivers/input/serio/hyperv-keyboard.c +F: drivers/pci/host/hv_pcifront.c F: drivers/net/hyperv/ F: drivers/scsi/storvsc_drv.c F: drivers/video/fbdev/hyperv_fb.c
drivers/pci/Kconfig +7 -0
@@ -118,4 +118,11 @@ config PCI_LABEL def_bool y if (DMI || ACPI) select NLS +config HYPERV_VPCI + tristate "Hyper-V PCI Frontend" + depends on PCI && X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && X86_64 + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from a PCI backend to support PCI driver domains. + source "drivers/pci/host/Kconfig"
drivers/pci/host/Makefile +1 -0
@@ -2,6 +2,7 @@ obj-$(CONFIG_PCIE_DW) += pcie-designware.o obj-$(CONFIG_PCI_DRA7XX) += pci-dra7xx.o obj-$(CONFIG_PCI_EXYNOS) += pci-exynos.o obj-$(CONFIG_PCI_IMX6) += pci-imx6.o +obj-$(CONFIG_HYPERV_VPCI) += hv_pcifront.o obj-$(CONFIG_PCI_MVEBU) += pci-mvebu.o obj-$(CONFIG_PCI_TEGRA) += pci-tegra.o obj-$(CONFIG_PCI_RCAR_GEN2) += pci-rcar-gen2.o
drivers/pci/host/hv_pcifront.c new file +2249 -0
2,249 lines not on this page · raw message
Signature · 1 line
1.9.1