RISC-V IPI Improvements
Subsystems (5)
v2 cover RISC-V IPI Improvements
This series aims to improve IPI support in Linux RISC-V in following ways:
1) Treat IPIs as normal per-CPU interrupts instead of having custom RISC-V specific hooks. This also makes Linux RISC-V IPI support aligned with other architectures.
2) Remote TLB flushes and icache flushes should prefer local IPIs instead of SBI calls whenever we have specialized hardware (such as RISC-V AIA IMSIC and RISC-V ACLINT) which allows S-mode software to directly inject IPIs without any assistance from M-mode runtime firmware.
These patches were already part of the "Linux RISC-V ACLINT Support" series but this now a separate series so that it can be merged independently of the "Linux RISC-V ACLINT Support" series.
(Refer, https://lore.kernel.org/lkml/[email protected]/)
These patches are also a preparatory patches for the up-coming:
1) Linux RISC-V ACLINT support
2) Linux RISC-V AIA support
3) KVM RISC-V TLB flush improvements
These patches can also be found in riscv_ipi_imp_v2 branch at:
https://github.com/avpatel/linux.git
Changes since v1:
- Use synthetic fwnode for INTC instead of irq_set_default_host() in PATCH2
Anup Patel (6):
RISC-V: Clear SIP bit only when using SBI IPI operations irqchip/riscv-intc: Create domain using named fwnode
RISC-V: Treat IPIs as normal Linux IRQs
RISC-V: Allow marking IPIs as suitable for remote FENCEs
RISC-V: Use IPIs for remote TLB flush when possible
RISC-V: Use IPIs for remote icache flush when possible
arch/riscv/Kconfig | 1 + arch/riscv/include/asm/ipi-mux.h | 45 ++++++ arch/riscv/include/asm/irq.h | 2 + arch/riscv/include/asm/sbi.h | 2 + arch/riscv/include/asm/smp.h | 49 +++++-- arch/riscv/kernel/Makefile | 1 + arch/riscv/kernel/cpu-hotplug.c | 3 +- arch/riscv/kernel/ipi-mux.c | 223 ++++++++++++++++++++++++++++++ arch/riscv/kernel/irq.c | 16 ++- arch/riscv/kernel/sbi.c | 18 ++- arch/riscv/kernel/smp.c | 164 +++++++++++----------- arch/riscv/kernel/smpboot.c | 5 +- arch/riscv/mm/cacheflush.c | 5 +- arch/riscv/mm/tlbflush.c | 93 +++++++++++-- drivers/clocksource/timer-clint.c | 21 ++- drivers/clocksource/timer-riscv.c | 11 +- drivers/irqchip/irq-riscv-intc.c | 67 ++++----- drivers/irqchip/irq-sifive-plic.c | 19 +-- 18 files changed, 563 insertions(+), 182 deletions(-) create mode 100644 arch/riscv/include/asm/ipi-mux.h create mode 100644 arch/riscv/kernel/ipi-mux.c
Signature · 1 line
2.25.1
PATCH v2 1/6 RISC-V: Clear SIP bit only when using SBI IPI operations
The software interrupt pending (i.e. [M|S]SIP) bit is writeable for S-mode but read-only for M-mode so we clear this bit only when using SBI IPI operations.
--- arch/riscv/kernel/sbi.c | 8 +++++++- arch/riscv/kernel/smp.c | 2 -- 2 files changed, 7 insertions(+), 3 deletions(-)
arch/riscv/kernel/sbi.c +7 -1
@@ -621,8 +621,14 @@ static void sbi_send_cpumask_ipi(const struct cpumask *target)sbi_send_ipi (target); } +static void sbi_ipi_clear (void ) +{ +csr_clear (CSR_IP ,IE_SIE ); +} +static const struct riscv_ipi_ops sbi_ipi_ops = { - .ipi_inject = sbi_send_cpumask_ipi + .ipi_inject = sbi_send_cpumask_ipi, + .ipi_clear = sbi_ipi_clear };void __init sbi_init (void )
arch/riscv/kernel/smp.c +0 -2
@@ -89,8 +89,6 @@ void riscv_clear_ipi(void) {if (ipi_ops && ipi_ops->ipi_clear) ipi_ops->ipi_clear (); - -csr_clear (CSR_IP ,IE_SIE ); }EXPORT_SYMBOL_GPL (riscv_clear_ipi);
Signature · 1 line
2.25.1
PATCH v2 2/6 irqchip/riscv-intc: Create domain using named fwnode
In reply to Anup PatelWe should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)
arch/riscv/include/asm/irq.h +2 -0
@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */
arch/riscv/kernel/irq.c +13 -0
@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h> +static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode); +int arch_show_interrupts (struct seq_file *p,int prec) {show_ipi_stats (p, prec);
drivers/clocksource/timer-clint.c +7 -6
@@ -149,6 +149,7 @@ static int __init clint_timer_init_dt(struct device_node *np)int rc;u32 i, nr_irqs;void __iomem *base; +struct irq_domain *domain;struct of_phandle_args oirq;/*
@@ -169,14 +170,14 @@ static int __init clint_timer_init_dt(struct device_node *np) np, i, oirq.args[0]);return -ENODEV ; } - -/* Find parent irq domain and map timer irq */ -if (!clint_timer_irq && - oirq.args[0 ] ==RV_IRQ_TIMER && -irq_find_host (oirq.np)) - clint_timer_irq =irq_of_parse_and_map (np, i); } +/* Find parent irq domain and map timer irq */ + domain =irq_find_matching_fwnode (riscv_intc_fwnode (), +DOMAIN_BUS_ANY ); +if (!clint_timer_irq && domain) + clint_timer_irq =irq_create_mapping (domain,RV_IRQ_TIMER ); +/* If CLINT timer irq not found then fail */ if (!clint_timer_irq) {pr_err ("%pOFP: timer irq not found\n" , np);
drivers/clocksource/timer-riscv.c +2 -9
@@ -102,7 +102,6 @@ static irqreturn_t riscv_timer_interrupt(int irq, void *dev_id)static int __init riscv_timer_init_dt (struct device_node *n) {int cpuid, hartid, error; -struct device_node *child;struct irq_domain *domain; hartid =riscv_of_processor_hartid (n);
@@ -121,14 +120,8 @@ static int __init riscv_timer_init_dt(struct device_node *n)if (cpuid !=smp_processor_id ())return 0 ; - domain =NULL ; - child =of_get_compatible_child (n,"riscv,cpu-intc" ); -if (!child) { -pr_err ("Failed to find INTC node [%pOF]\n" , n); -return -ENODEV ; - } - domain =irq_find_host (child); -of_node_put (child); + domain =irq_find_matching_fwnode (riscv_intc_fwnode (), +DOMAIN_BUS_ANY );if (!domain) {pr_err ("Failed to find IRQ domain for node [%pOF]\n" , n);return -ENODEV ;
drivers/irqchip/irq-riscv-intc.c +10 -2
@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node,if (riscv_hartid_to_cpuid (hartid) !=smp_processor_id ())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL ); +/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );if (!intc_domain) {pr_err ("unable to add IRQ domain\n" );return -ENXIO ;
drivers/irqchip/irq-sifive-plic.c +11 -8
@@ -284,6 +284,7 @@ static int __init plic_init(struct device_node *node,u32 nr_irqs;struct plic_priv *priv;struct plic_handler *handler; +struct irq_domain *domain; priv =kzalloc (sizeof (*priv),GFP_KERNEL );if (!priv)
@@ -339,14 +340,6 @@ static int __init plic_init(struct device_node *node,continue ; } -/* Find parent domain and register chained handler */ -if (!plic_parent_irq &&irq_find_host (parent.np)) { - plic_parent_irq =irq_of_parse_and_map (node, i); -if (plic_parent_irq) -irq_set_chained_handler (plic_parent_irq, - plic_handle_irq); - } -/* * When running in M-mode we need to ignore the S-mode handler. * Here we assume it always comes later, but that might be a
@@ -373,6 +366,16 @@ static int __init plic_init(struct device_node *node, nr_handlers++; } +/* Find parent domain and register chained handler */ + domain =irq_find_matching_fwnode (riscv_intc_fwnode (), +DOMAIN_BUS_ANY ); +if (!plic_parent_irq && domain) { + plic_parent_irq =irq_create_mapping (domain,RV_IRQ_EXT ); +if (plic_parent_irq) +irq_set_chained_handler (plic_parent_irq, + plic_handle_irq); + } +/* * We can have multiple PLIC instances so setup cpuhp state only * when context handler for current/boot CPU is present.
Signature · 1 line
2.25.1
PATCH v2 3/6 RISC-V: Treat IPIs as normal Linux IRQs
In reply to Anup PatelCurrently, the RISC-V kernel provides arch specific hooks (i.e. struct riscv_ipi_ops) to register IPI handling methods. The stats gathering of IPIs is also arch specific in the RISC-V kernel.
Other architectures (such as ARM, ARM64, and MIPS) have moved away from custom arch specific IPI handling methods. Currently, these architectures have Linux irqchip drivers providing a range of Linux IRQ numbers to be used as IPIs and IPI triggering is done using generic IPI APIs. This approach allows architectures to treat IPIs as normal Linux IRQs and IPI stats gathering is done by the generic Linux IRQ subsystem.
We extend the RISC-V IPI handling as-per above approach so that arch specific IPI handling methods (struct riscv_ipi_ops) can be removed and the IPI handling is totally contained within Linux irqchip drivers.
--- arch/riscv/Kconfig | 1 + arch/riscv/include/asm/ipi-mux.h | 43 ++++++ arch/riscv/include/asm/sbi.h | 2 + arch/riscv/include/asm/smp.h | 35 +++-- arch/riscv/kernel/Makefile | 1 + arch/riscv/kernel/cpu-hotplug.c | 3 +- arch/riscv/kernel/ipi-mux.c | 222 ++++++++++++++++++++++++++++++ arch/riscv/kernel/irq.c | 3 +- arch/riscv/kernel/sbi.c | 13 +- arch/riscv/kernel/smp.c | 153 ++++++++++---------- arch/riscv/kernel/smpboot.c | 5 +- drivers/clocksource/timer-clint.c | 8 +- drivers/irqchip/irq-riscv-intc.c | 55 ++++---- 13 files changed, 405 insertions(+), 139 deletions(-) create mode 100644 arch/riscv/include/asm/ipi-mux.h create mode 100644 arch/riscv/kernel/ipi-mux.c
arch/riscv/Kconfig +1 -0
@@ -54,6 +54,7 @@ config RISCV select GENERIC_GETTIMEOFDAY if HAVE_GENERIC_VDSO select GENERIC_IDLE_POLL_SETUP select GENERIC_IOREMAP if MMU + select GENERIC_IRQ_IPI select GENERIC_IRQ_MULTI_HANDLER select GENERIC_IRQ_SHOW select GENERIC_IRQ_SHOW_LEVEL
arch/riscv/include/asm/ipi-mux.h new file +43 -0
43 lines not on this page · raw message
arch/riscv/include/asm/sbi.h +2 -0
@@ -116,6 +116,7 @@ struct sbiret { };void sbi_init (void ); +void sbi_ipi_init (void ); struct sbiret sbi_ecall(int ext, int fid, unsigned long arg0, unsigned long arg1, unsigned long arg2, unsigned long arg3, unsigned long arg4,
@@ -185,6 +186,7 @@ static inline unsigned long sbi_mk_version(unsigned long major,int sbi_err_map_linux_errno (int err);#else /* CONFIG_RISCV_SBI */ static inline int sbi_remote_fence_i (const struct cpumask *cpu_mask) {return -1 ; } +static inline void sbi_ipi_init (void ) { }static inline void sbi_init (void ) {}#endif /* CONFIG_RISCV_SBI */ #endif /* _ASM_RISCV_SBI_H */
arch/riscv/include/asm/smp.h +21 -14
@@ -15,11 +15,6 @@struct seq_file ;extern unsigned long boot_cpu_hartid; -struct riscv_ipi_ops { -void (*ipi_inject)(const struct cpumask *target); -void (*ipi_clear)(void ); -}; -#ifdef CONFIG_SMP /* * Mapping between linux logical cpu index and hartid.
@@ -33,9 +28,6 @@ void show_ipi_stats(struct seq_file *p, int prec);/* SMP initialization hook for setup_arch */ void __init setup_smp (void ); -/* Called from C code, this handles an IPI. */ -void handle_IPI (struct pt_regs *regs); -/* Hook for the generic smp_call_function_many() routine. */ void arch_send_call_function_ipi_mask (struct cpumask *mask);
@@ -44,11 +36,17 @@ void arch_send_call_function_single_ipi(int cpu);int riscv_hartid_to_cpuid (int hartid); -/* Set custom IPI operations */ -void riscv_set_ipi_ops (const struct riscv_ipi_ops *ops); +/* Enable IPI for CPU hotplug */ +void riscv_ipi_enable (void ); + +/* Disable IPI for CPU hotplug */ +void riscv_ipi_disable (void ); -/* Clear IPI for current CPU */ -void riscv_clear_ipi (void ); +/* Check if IPI interrupt numbers are available */ +bool riscv_ipi_have_virq_range (void ); + +/* Set the IPI interrupt numbers for arch (called by irqchip drivers) */ +void riscv_ipi_set_virq_range (int virq,int nr_irqs);/* Secondary hart entry */ asmlinkage void smp_callin(void);
@@ -82,11 +80,20 @@ static inline unsigned long cpuid_to_hartid_map(int cpu)return boot_cpu_hartid; } -static inline void riscv_set_ipi_ops (const struct riscv_ipi_ops *ops) +static inline void riscv_ipi_enable (void ) { } -static inline void riscv_clear_ipi (void ) +static inline void riscv_ipi_disable (void ) +{ +} + +static inline bool riscv_ipi_have_virq_range (void ) +{ +return false; +} + +static inline void riscv_ipi_set_virq_range (int virq,int nr) { }
arch/riscv/kernel/Makefile +1 -0
@@ -42,6 +42,7 @@ obj-$(CONFIG_RISCV_M_MODE) += traps_misaligned.o obj-$(CONFIG_FPU) += fpu.o obj-$(CONFIG_SMP) += smpboot.o obj-$(CONFIG_SMP) += smp.o +obj-$(CONFIG_SMP) += ipi-mux.o obj-$(CONFIG_SMP) += cpu_ops.o obj-$(CONFIG_RISCV_BOOT_SPINWAIT) += cpu_ops_spinwait.o
arch/riscv/kernel/cpu-hotplug.c +2 -1
@@ -12,7 +12,7 @@#include <linux/sched/hotplug.h> #include <asm/irq.h> #include <asm/cpu_ops.h> -#include <asm/sbi.h> +#include <asm/smp.h> bool cpu_has_hotplug (unsigned int cpu) {
@@ -41,6 +41,7 @@ int __cpu_disable(void)remove_cpu_topology (cpu);set_cpu_online (cpu, false); +riscv_ipi_disable ();irq_migrate_all_off_this_cpu ();return ret;
arch/riscv/kernel/ipi-mux.c new file +222 -0
222 lines not on this page · raw message
arch/riscv/kernel/irq.c +2 -1
@@ -10,7 +10,7 @@#include <linux/irqdomain.h> #include <linux/module.h> #include <linux/seq_file.h> -#include <asm/smp.h> +#include <asm/sbi.h> static struct fwnode_handle *intc_fwnode;
@@ -34,4 +34,5 @@ void __init init_IRQ(void)irqchip_init ();if (!handle_arch_irq)panic ("No interrupt controller found." ); +sbi_ipi_init (); }
arch/riscv/kernel/sbi.c +7 -6
@@ -5,9 +5,11 @@* Copyright (c) 2020 Western Digital Corporation or its affiliates. */ +#define pr_fmt (fmt) "riscv: " fmt#include <linux/init.h> #include <linux/pm.h> #include <linux/reboot.h> +#include <asm/ipi-mux.h> #include <asm/sbi.h> #include <asm/smp.h>
@@ -626,10 +628,11 @@ static void sbi_ipi_clear(void)csr_clear (CSR_IP ,IE_SIE ); } -static const struct riscv_ipi_ops sbi_ipi_ops = { - .ipi_inject = sbi_send_cpumask_ipi, - .ipi_clear = sbi_ipi_clear -}; +void __init sbi_ipi_init (void ) +{ +if (riscv_ipi_mux_create (true, sbi_ipi_clear, sbi_send_cpumask_ipi)) +pr_info ("providing IPIs using SBI IPI extension\n" ); +}void __init sbi_init (void ) {
@@ -677,6 +680,4 @@ void __init sbi_init(void) __sbi_send_ipi = __sbi_send_ipi_v01; __sbi_rfence = __sbi_rfence_v01; } - -riscv_set_ipi_ops (&sbi_ipi_ops); }
arch/riscv/kernel/smp.c +76 -77
204 lines not on this page · raw message
arch/riscv/kernel/smpboot.c +2 -3
@@ -30,7 +30,6 @@#include <asm/numa.h> #include <asm/tlbflush.h> #include <asm/sections.h> -#include <asm/sbi.h> #include <asm/smp.h> #include <asm/alternative.h>
@@ -159,12 +158,12 @@ asmlinkage __visible void smp_callin(void)struct mm_struct *mm = &init_mm;unsigned int curr_cpuid =smp_processor_id (); -riscv_clear_ipi (); -/* All kernel threads share the same mm context. */ mmgrab (mm); current->active_mm = mm; +riscv_ipi_enable (); +notify_cpu_starting (curr_cpuid);numa_add_cpu (curr_cpuid);update_siblings_masks (curr_cpuid);
drivers/clocksource/timer-clint.c +2 -6
@@ -20,6 +20,7 @@#include <linux/of_irq.h> #include <linux/smp.h> #include <linux/timex.h> +#include <asm/ipi-mux.h> #ifndef CONFIG_RISCV_M_MODE #include <asm/clint.h>
@@ -54,11 +55,6 @@ static void clint_clear_ipi(void)writel (0 , clint_ipi_base +cpuid_to_hartid_map (smp_processor_id ())); } -static struct riscv_ipi_ops clint_ipi_ops = { - .ipi_inject = clint_send_ipi, - .ipi_clear = clint_clear_ipi, -}; -#ifdef CONFIG_64BIT #define clint_get_cycles () readq_relaxed(clint_timer_val)#else
@@ -229,7 +225,7 @@ static int __init clint_timer_init_dt(struct device_node *np) goto fail_free_irq; } -riscv_set_ipi_ops (&clint_ipi_ops); +riscv_ipi_mux_create (true, clint_clear_ipi, clint_send_ipi);clint_clear_ipi ();return 0 ;
drivers/irqchip/irq-riscv-intc.c +24 -31
82 lines not on this page · raw message
Signature · 1 line
2.25.1
PATCH v2 4/6 RISC-V: Allow marking IPIs as suitable for remote FENCEs
In reply to Anup PatelTo do remote FENCEs (i.e. remote TLB flushes) using IPI calls on the RISC-V kernel, we need hardware mechanism to directly inject IPI from the RISC-V kernel instead of using SBI calls.
The upcoming ACLINT [M|S]SWI devices and AIA IMSIC devices allow direct IPI injection from the RISC-V kernel. To support this, we extend the riscv_ipi_set_virq_range() function so that irqchip drivers can mark IPIs as suitable for remote FENCEs.
--- arch/riscv/include/asm/ipi-mux.h | 2 ++ arch/riscv/include/asm/smp.h | 18 ++++++++++++++++-- arch/riscv/kernel/ipi-mux.c | 3 ++- arch/riscv/kernel/sbi.c | 3 ++- arch/riscv/kernel/smp.c | 11 ++++++++++- drivers/clocksource/timer-clint.c | 2 +- 6 files changed, 33 insertions(+), 6 deletions(-)
arch/riscv/include/asm/ipi-mux.h +2 -0
@@ -15,6 +15,7 @@ void riscv_ipi_mux_handle_irq(void);/* Create irq_domain for muxed IPIs */ struct irq_domain *riscv_ipi_mux_create (bool use_soft_irq, +bool use_for_rfence,void (*clear_ipi)(void ),void (*send_ipi)(const struct cpumask *mask));
@@ -28,6 +29,7 @@ static inline void riscv_ipi_mux_handle_irq(void) }static inline struct irq_domain *riscv_ipi_mux_create (bool use_soft_irq, +bool use_for_rfence,void (*clear_ipi)(void ),void (*send_ipi)(const struct cpumask *mask)) {
arch/riscv/include/asm/smp.h +16 -2
@@ -16,6 +16,9 @@ struct seq_file;extern unsigned long boot_cpu_hartid;#ifdef CONFIG_SMP + +#include <linux/jump_label.h> +/* * Mapping between linux logical cpu index and hartid. */
@@ -46,7 +49,12 @@ void riscv_ipi_disable(void);bool riscv_ipi_have_virq_range (void );/* Set the IPI interrupt numbers for arch (called by irqchip drivers) */ -void riscv_ipi_set_virq_range (int virq,int nr_irqs); +void riscv_ipi_set_virq_range (int virq,int nr_irqs,bool use_for_rfence); + +/* Check if we can use IPIs for remote FENCEs */ +DECLARE_STATIC_KEY_FALSE (riscv_ipi_for_rfence); +#define riscv_use_ipi_for_rfence () \ + static_branch_unlikely(&riscv_ipi_for_rfence)/* Secondary hart entry */ asmlinkage void smp_callin(void);
@@ -93,10 +101,16 @@ static inline bool riscv_ipi_have_virq_range(void) return false; } -static inline void riscv_ipi_set_virq_range (int virq,int nr) +static inline void riscv_ipi_set_virq_range (int virq,int nr, +bool use_for_rfence) { } +static inline bool riscv_use_ipi_for_rfence (void ) +{ +return false; +} +#endif /* CONFIG_SMP */ #if defined(CONFIG_HOTPLUG_CPU ) && (CONFIG_SMP )
arch/riscv/kernel/ipi-mux.c +2 -1
@@ -144,6 +144,7 @@ static int ipi_mux_starting_cpu(unsigned int cpu) }struct irq_domain *riscv_ipi_mux_create (bool use_soft_irq, +bool use_for_rfence,void (*clear_ipi)(void ),void (*send_ipi)(const struct cpumask *mask)) {
@@ -198,7 +199,7 @@ struct irq_domain *riscv_ipi_mux_create(bool use_soft_irq,"irqchip/riscv/ipi-mux:starting" , ipi_mux_starting_cpu, ipi_mux_dying_cpu); -riscv_ipi_set_virq_range (virq,BITS_PER_LONG ); +riscv_ipi_set_virq_range (virq,BITS_PER_LONG , use_for_rfence);return ipi_mux_priv.domain;
arch/riscv/kernel/sbi.c +2 -1
@@ -630,7 +630,8 @@ static void sbi_ipi_clear(void)void __init sbi_ipi_init (void ) { -if (riscv_ipi_mux_create (true, sbi_ipi_clear, sbi_send_cpumask_ipi)) +if (riscv_ipi_mux_create (true, false, + sbi_ipi_clear, sbi_send_cpumask_ipi))pr_info ("providing IPIs using SBI IPI extension\n" ); }
arch/riscv/kernel/smp.c +10 -1
@@ -149,7 +149,10 @@ bool riscv_ipi_have_virq_range(void)return (ipi_virq_base) ? true : false; } -void riscv_ipi_set_virq_range (int virq,int nr) +DEFINE_STATIC_KEY_FALSE (riscv_ipi_for_rfence); +EXPORT_SYMBOL_GPL (riscv_ipi_for_rfence); + +void riscv_ipi_set_virq_range (int virq,int nr,bool use_for_rfence) {int i, err;
@@ -172,6 +175,12 @@ void riscv_ipi_set_virq_range(int virq, int nr)/* Enabled IPIs for boot CPU immediately */ riscv_ipi_enable (); + +/* Update RFENCE static key */ +if (use_for_rfence) +static_branch_enable (&riscv_ipi_for_rfence); +else +static_branch_disable (&riscv_ipi_for_rfence); }EXPORT_SYMBOL_GPL (riscv_ipi_set_virq_range);
drivers/clocksource/timer-clint.c +1 -1
@@ -225,7 +225,7 @@ static int __init clint_timer_init_dt(struct device_node *np) goto fail_free_irq; } -riscv_ipi_mux_create (true, clint_clear_ipi, clint_send_ipi); +riscv_ipi_mux_create (true, true, clint_clear_ipi, clint_send_ipi);clint_clear_ipi ();return 0 ;
Signature · 7 lines
2.25.1 _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
PATCH v2 5/6 RISC-V: Use IPIs for remote TLB flush when possible
In reply to Anup PatelIf IPI calls are injected using SBI IPI calls then remote TLB flush using SBI RFENCE calls is much faster because using IPIs for remote TLB flush would still endup as SBI IPI calls with extra processing on kernel side.
It is now possible to have specialized hardware (such as RISC-V AIA and RISC-V ACLINT) which allows S-mode software to directly inject IPIs without any assistance from M-mode runtime firmware.
This patch extends remote TLB flush functions to use IPIs whenever underlying IPI operations are suitable for remote FENCEs.
--- arch/riscv/mm/tlbflush.c | 93 +++++++++++++++++++++++++++++++++------- 1 file changed, 78 insertions(+), 15 deletions(-)
arch/riscv/mm/tlbflush.c +78 -15
@@ -23,14 +23,62 @@ static inline void local_flush_tlb_page_asid(unsigned long addr, : "memory"); } +static inline void local_flush_tlb_range (unsigned long start, +unsigned long size,unsigned long stride) +{ +if (size <= stride) +local_flush_tlb_page (start); +else +local_flush_tlb_all (); +} + +static inline void local_flush_tlb_range_asid (unsigned long start, +unsigned long size,unsigned long stride,unsigned long asid) +{ +if (size <= stride) +local_flush_tlb_page_asid (start, asid); +else +local_flush_tlb_all_asid (asid); +} + +static void __ipi_flush_tlb_all (void *info) +{ +local_flush_tlb_all (); +} +void flush_tlb_all (void ) { -sbi_remote_sfence_vma (NULL ,0 ,-1 ); +if (riscv_use_ipi_for_rfence ()) +on_each_cpu (__ipi_flush_tlb_all,NULL ,1 ); +else +sbi_remote_sfence_vma (NULL ,0 ,-1 ); +} + +struct flush_tlb_range_data { +unsigned long asid; +unsigned long start; +unsigned long size; +unsigned long stride; +}; + +static void __ipi_flush_tlb_range_asid (void *info) +{ +struct flush_tlb_range_data *d = info; + +local_flush_tlb_range_asid (d->start, d->size, d->stride, d->asid); +} + +static void __ipi_flush_tlb_range (void *info) +{ +struct flush_tlb_range_data *d = info; + +local_flush_tlb_range (d->start, d->size, d->stride); } -static void __sbi_tlb_flush_range (struct mm_struct *mm,unsigned long start, -unsigned long size,unsigned long stride) +static void __flush_tlb_range (struct mm_struct *mm,unsigned long start, +unsigned long size,unsigned long stride) { +struct flush_tlb_range_data ftd;struct cpumask *cmask =mm_cpumask (mm);unsigned int cpuid;bool broadcast;
@@ -45,19 +93,34 @@ static void __sbi_tlb_flush_range(struct mm_struct *mm, unsigned long start,unsigned long asid =atomic_long_read (&mm->context.id);if (broadcast) { -sbi_remote_sfence_vma_asid (cmask, start, size, asid); - }else if (size <= stride) { -local_flush_tlb_page_asid (start, asid); +if (riscv_use_ipi_for_rfence ()) { + ftd.asid = asid; + ftd.start = start; + ftd.size = size; + ftd.stride = stride; +on_each_cpu_mask (cmask, + __ipi_flush_tlb_range_asid, + &ftd,1 ); + }else +sbi_remote_sfence_vma_asid (cmask, + start, size, asid); }else { -local_flush_tlb_all_asid (asid); +local_flush_tlb_range_asid (start, size, stride, asid); } }else {if (broadcast) { -sbi_remote_sfence_vma (cmask, start, size); - }else if (size <= stride) { -local_flush_tlb_page (start); +if (riscv_use_ipi_for_rfence ()) { + ftd.asid =0 ; + ftd.start = start; + ftd.size = size; + ftd.stride = stride; +on_each_cpu_mask (cmask, + __ipi_flush_tlb_range, + &ftd,1 ); + }else +sbi_remote_sfence_vma (cmask, start, size); }else { -local_flush_tlb_all (); +local_flush_tlb_range (start, size, stride); } }
@@ -66,23 +129,23 @@ static void __sbi_tlb_flush_range(struct mm_struct *mm, unsigned long start,void flush_tlb_mm (struct mm_struct *mm) { -__sbi_tlb_flush_range (mm,0 ,-1 ,PAGE_SIZE ); +__flush_tlb_range (mm,0 ,-1 ,PAGE_SIZE ); }void flush_tlb_page (struct vm_area_struct *vma,unsigned long addr) { -__sbi_tlb_flush_range (vma->vm_mm, addr,PAGE_SIZE ,PAGE_SIZE ); +__flush_tlb_range (vma->vm_mm, addr,PAGE_SIZE ,PAGE_SIZE ); }void flush_tlb_range (struct vm_area_struct *vma,unsigned long start,unsigned long end) { -__sbi_tlb_flush_range (vma->vm_mm, start, end - start,PAGE_SIZE ); +__flush_tlb_range (vma->vm_mm, start, end - start,PAGE_SIZE ); }#ifdef CONFIG_TRANSPARENT_HUGEPAGE void flush_pmd_tlb_range (struct vm_area_struct *vma,unsigned long start,unsigned long end) { -__sbi_tlb_flush_range (vma->vm_mm, start, end - start,PMD_SIZE ); +__flush_tlb_range (vma->vm_mm, start, end - start,PMD_SIZE ); }#endif
Signature · 1 line
2.25.1
PATCH v2 6/6 RISC-V: Use IPIs for remote icache flush when possible
In reply to Anup PatelIf IPI calls are injected using SBI IPI calls then remote icache flush using SBI RFENCE calls is much faster because using IPIs for remote icache flush would still endup as SBI IPI calls with extra processing on the kernel side.
It is now possible to have specialized hardware (such as RISC-V AIA and RISC-V ACLINT) which allows S-mode software to directly inject IPIs without any assistance from M-mode runtime firmware.
This patch extends remote icache flush functions to use IPIs whenever underlying IPI operations are suitable for remote FENCEs.
--- arch/riscv/mm/cacheflush.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
arch/riscv/mm/cacheflush.c +3 -2
@@ -18,7 +18,7 @@ void flush_icache_all(void) {local_flush_icache_all (); -if (IS_ENABLED (CONFIG_RISCV_SBI )) +if (IS_ENABLED (CONFIG_RISCV_SBI ) && !riscv_use_ipi_for_rfence ())sbi_remote_fence_i (NULL );else on_each_cpu (ipi_remote_fence_i,NULL ,1 );
@@ -66,7 +66,8 @@ void flush_icache_mm(struct mm_struct *mm, bool local)* with flush_icache_deferred(). */ smp_mb (); - }else if (IS_ENABLED (CONFIG_RISCV_SBI )) { + }else if (IS_ENABLED (CONFIG_RISCV_SBI ) && + !riscv_use_ipi_for_rfence ()) {sbi_remote_fence_i (&others); }else {on_each_cpu_mask (&others, ipi_remote_fence_i,NULL ,1 );
Signature · 1 line
2.25.1
Re: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
In reply to Anup PatelQuoted 42 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h>
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);
Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
what you should have instead is something like:
static struct fwnode_handle *(*__get_root_intc_node)(void); struct fwnode_handle *riscv_get_root_intc_hwnode(void)
{
if (__get_root_intc_node)
return __get_root_intc_node();
return NULL;
}and the corresponding registration interface.
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for duplicate entries).
Quoted 11 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );
drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );
This is what I'm talking about. It is simply broken. So either you don't need a per-CPU node (and the DT was bad the first place), or you absolutely need one (and the whole 'well-known/default domain' doesn't work at all).
Either way, this patch is plain wrong.
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
Anup Patel
maintainerRe: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
Quoted 45 lines · Marc Zyngier
Quoted 43 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h>
Quoted 15 lines
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
Fair enough, I will update this patch to not create a synthetic fwnode.
The issue is not with INTC driver. We have other drivers and places (such as SBI IPI driver, SBI PMU driver, and KVM RISC-V AIA support) where we don't have a way to locate INTC fwnode.
Quoted 5 lines
what you should have instead is something like:
static struct
fwnode_handle*(*__get_root_intc_node)(void); structfwnode_handle*riscv_get_root_intc_hwnode(void)
Quoted 8 lines
{ if (__get_root_intc_node) return __get_root_intc_node(); return NULL; }and the corresponding registration interface.
Thanks, I will follow this suggestion. This is a much better approach and it will avoid touching existing drivers.
Quoted 34 lines
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for duplicate entries).
Quoted 12 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );This is what I'm talking about. It is simply broken. So either you don't need a per-CPU node (and the DT was bad the first place), or you absolutely need
one (and the whole 'well-known/default domain' doesn't work at all).
Quoted 1 line
Either way, this patch is plain wrong.
Okay, I will update this patch with the new approach which you suggested.
Regards,
Anup
Quoted 5 lines
M.--
Jazz is not dead. It just smells funny...
Re: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
Quoted 62 lines · Anup Patel
Quoted 45 lines · Marc Zyngier
Quoted 43 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h> Quoted 15 lines
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
Quoted 5 lines
Fair enough, I will update this patch to not create a synthetic fwnode.
The issue is not with INTC driver. We have other drivers and places (such as SBI IPI driver, SBI PMU driver, and KVM RISC-V AIA support) where we don't have a way to locate INTC fwnode.
And that's exactly what I am talking about: The INTC is OK (sort of), but the firmware is too crap for words, and isn't even able to expose where the various endpoints route their interrupts to.
Yes, this is probably fine today because you can describe the topology of RISC-V systems on the surface of a post stamp. Once you get to the complexity of a server-grade SoC (or worse, a mobile phone style SoC), this *implicit topology* stuff doesn't fly, because there is no guarantee that all endpoints will always all point to the same controller.
Quoted 50 lines
Quoted 4 lines
what you should have instead is something like:
static struct
fwnode_handle*(*__get_root_intc_node)(void); structfwnode_handle*riscv_get_root_intc_hwnode(void)Quoted 8 lines
{ if (__get_root_intc_node) return __get_root_intc_node(); return NULL; }and the corresponding registration interface.
Thanks, I will follow this suggestion. This is a much better approach and it will avoid touching existing drivers.
Quoted 34 lines
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for duplicate entries).
Quoted 12 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );This is what I'm talking about. It is simply broken. So either you don't need a per-CPU node (and the DT was bad the first place), or you absolutely need
one (and the whole 'well-known/default domain' doesn't work at all).
Quoted 3 lines
Quoted 1 line
Either way, this patch is plain wrong.
Okay, I will update this patch with the new approach which you suggested.
But how do you plan to work around the fact that everything is currently build around having a node (and an irqdomain) per CPU? The PLIC, for example, clearly has one parent per CPU, not one global parent.
I'm sure there was a good reason for this, and I suspect merging the domains will simply end up breaking things.
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
Anup Patel
maintainerRe: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
Quoted 66 lines · Marc Zyngier
Quoted 64 lines · Anup Patel
Quoted 45 lines · Marc Zyngier
Quoted 43 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h> Quoted 15 lines
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
Fair enough, I will update this patch to not create a synthetic fwnode.
Quoted 7 lines
Quoted 3 lines
The issue is not with INTC driver. We have other drivers and places (such as SBI IPI driver, SBI PMU driver, and KVM RISC-V AIA support) where we don't have a way to locate INTC fwnode.
And that's exactly what I am talking about: The INTC is OK (sort of), but the firmware is too crap for words, and isn't even able to expose where the various endpoints route their interrupts to.
The firmware is always present at a higher privilege-level hence there is no DT node to discover the presence of firmware. The local interrupts used by the firmware for IPI, Timer and PMU are defined by the RISC-V ISA specification.
Quoted 7 lines
Yes, this is probably fine today because you can describe the topology of RISC-V systems on the surface of a post stamp. Once you get to the complexity of a server-grade SoC (or worse, a mobile phone style SoC), this *implicit topology* stuff doesn't fly, because there is no guarantee
that all endpoints will always all point to the same controller.
The local interrupts (per-CPU) are always managed by the INTC. The interrupt controllers to manage device interrupts (such as PLIC) can vary from platform to platform and have INTC as the parent domain.
We already have high-end interrupt controllers (such as AIA) under development which are scalable for server-grade SoC, mobile SoC and various other types of SoCs.
We are able to describe the topology of different types of interrupt controllers (PLIC as well as AIA) in DT.
The only issue is for drivers which do not have dedicated DT node (such as SBI IPI, SBI Timer, SBI PMU, or KVM RISC-V) but the upside is that local interrupt numbers used by these drivers is clearly defined by the RISC-V ISA specification:
Here are the local interrupts defined by the RISC-V ISA spec:
IRQ13 => PMU overflow interrupt (used by SBI PMU driver) IRQ12 => S-mode guest external interrupt (to be used by KVM RISC-V) IRQ11 => M-mode external interrupt (used by firmware)
IRQ9 => S-mode external interrupt (used by PLIC driver) IRQ7 => M-mode timer interrupt IRQ5 => S-mode timer interrupt (used by SBI Timer driver) IRQ3 => M-mode software interrupt (used by firmware)
IRQ1 => S-mode software interrupt (used by SBI IPI driver)
Quoted 58 lines
Quoted 53 lines
Quoted 5 lines
what you should have instead is something like:
static struct
fwnode_handle*(*__get_root_intc_node)(void); structfwnode_handle*riscv_get_root_intc_hwnode(void)Quoted 8 lines
{ if (__get_root_intc_node) return __get_root_intc_node(); return NULL; }and the corresponding registration interface.
Thanks, I will follow this suggestion. This is a much better approach and it will avoid touching existing drivers.
Quoted 36 lines
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for
duplicate entries).Quoted 12 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );This is what I'm talking about. It is simply broken. So either you don't
need a per-CPU node (and the DT was bad the first place), or you absolutely need
one (and the whole 'well-known/default domain' doesn't work at all).Quoted 4 lines
Quoted 1 line
Either way, this patch is plain wrong.
Okay, I will update this patch with the new approach which you suggested.
Quoted 8 lines
But how do you plan to work around the fact that everything is currently build around having a node (and an irqdomain) per CPU? The PLIC, for example,
clearly has one parent per CPU, not one global parent.I'm sure there was a good reason for this, and I suspect merging the domains
will simply end up breaking things.
We can have multiple PLIC instances in a platform and each PLIC instance targets a subset of CPUs. Further, each PLIC instance has multiple PLIC contexts for associated CPUs.
The per-CPU INTC DT nodes and the "interrupts-extended" DT property of PLIC DT node helps us describe the association between various PLIC contexts and CPUs.
Here's an example PLIC DT node:
plic: interrupt-controller@c000000 {
#address-cells = <0>;
#interrupt-cells = <1>;
compatible = "sifive,fu540-c000-plic", "sifive,plic-1.0.0";
interrupt-controller;
interrupts-extended = <&cpu0_intc 11>,
<&cpu1_intc 11>, <&cpu1_intc 9>,
<&cpu2_intc 11>, <&cpu2_intc 9>,
<&cpu3_intc 11>, <&cpu3_intc 9>,
<&cpu4_intc 11>, <&cpu4_intc 9>;
reg = <0xc000000 0x4000000>;
riscv,ndev = <10>;
};In above above example, PLIC has 9 contexts and context to CPU connections are as follows:
PLIC context0 => CPU0 M-mode external interrupt PLIC context1 => CPU1 M-mode external interrupt PLIC context2 => CPU1 S-mode external interrupt PLIC context3 => CPU2 M-mode external interrupt PLIC context4 => CPU2 S-mode external interrupt
....
This is just one example and we can describe any kind of PLIC context to CPU connections using "interrupts-extended" DT property.
The same level of flexibility is provided by AIA interrupt controllers which are under development.
Regards,
Anup
Quoted 4 lines
M.--
Jazz is not dead. It just smells funny...
Re: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
In reply to Marc ZyngierQuoted 118 lines · Marc Zyngier
Quoted 59 lines · Anup Patel
Quoted 44 lines · Marc Zyngier
Quoted 43 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h> Quoted 14 lines
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
Quoted 4 lines
Fair enough, I will update this patch to not create a synthetic fwnode. The issue is not with INTC driver. We have other drivers and places (such as SBI IPI driver, SBI PMU driver, and KVM RISC-V AIA support) where we don't have a way to locate INTC fwnode.
And that's exactly what I am talking about: The INTC is OK (sort of), but the firmware is too crap for words, and isn't even able to expose where the various endpoints route their interrupts to.
Yes, this is probably fine today because you can describe the topology of RISC-V systems on the surface of a post stamp. Once you get to the complexity of a server-grade SoC (or worse, a mobile phone style SoC), this *implicit topology* stuff doesn't fly, because there is no guarantee that all endpoints will always all point to the same controller.
Quoted 42 lines
Quoted 9 lines
what you should have instead is something like:
static structfwnode_handle*(*__get_root_intc_node)(void); structfwnode_handle*riscv_get_root_intc_hwnode(void){ if (__get_root_intc_node) return __get_root_intc_node(); return NULL; }and the corresponding registration interface.
Thanks, I will follow this suggestion. This is a much better approach and it will avoid touching existing drivers.
Quoted 31 lines
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for duplicate entries).
Quoted 12 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );This is what I'm talking about. It is simply broken. So either you don't need a per-CPU node (and the DT was bad the first place), or you absolutely need
one (and the whole 'well-known/default domain' doesn't work at all). Either way, this patch is plain wrong.
Quoted 8 lines
Quoted 1 line
Okay, I will update this patch with the new approach which you suggested.
But how do you plan to work around the fact that everything is currently build around having a node (and an irqdomain) per CPU? The PLIC, for example, clearly has one parent per CPU, not one global parent.
I'm sure there was a good reason for this, and I suspect merging the domains will simply end up breaking things.
On the contrary, the drivers rely on the controller being the same across all harts, with riscv_intc_init skipping initialisation for all but the boot hart’s controller. The bindings are a complete pain to deal with as a result, what you *want* is like you have in the Arm world where there is just one interrupt controller in the device tree with some of the interrupts per-processor, but instead we have this overengineered nuisance. The only reason there are per-hart interrupt controllers is because that’s how the contexts for the CLINT/PLIC are specified, but that really should have been done another way rather than abusing the interrupts-extended property for that. In the FreeBSD world we’ve been totally ignoring the device tree nodes for the local interrupt controllers but for my AIA and ACLINT branch I started a few months ago (though ACLINT's now been completely screwed up by RVI politics, things have been renamed and split up differently in the past few days and software interrupts de-prioritised with no current path to ratification, so that was a waste of my time) I just hang the driver off the boot hart’s node and leave all the others as totally ignored and a waste of space other than to figure out the contexts for the PLIC etc.
TL;DR yes the bindings are awful, no there’s no issue with merging the domains.
Jess
Re: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
In reply to Anup PatelQuoted 88 lines · Anup Patel
Quoted 66 lines · Marc Zyngier
Quoted 64 lines · Anup Patel
Quoted 45 lines · Marc Zyngier
Quoted 43 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h> Quoted 15 lines
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
Fair enough, I will update this patch to not create a synthetic fwnode.
Quoted 7 lines
Quoted 3 lines
The issue is not with INTC driver. We have other drivers and places (such as SBI IPI driver, SBI PMU driver, and KVM RISC-V AIA support) where we don't have a way to locate INTC fwnode.
And that's exactly what I am talking about: The INTC is OK (sort of), but the firmware is too crap for words, and isn't even able to expose where the various endpoints route their interrupts to.
The firmware is always present at a higher privilege-level hence there is no DT node to discover the presence of firmware. The local interrupts used by the firmware for IPI, Timer and PMU are defined by the RISC-V ISA specification.
Quoted 7 lines
Yes, this is probably fine today because you can describe the topology of RISC-V systems on the surface of a post stamp. Once you get to the complexity of a server-grade SoC (or worse, a mobile phone style SoC), this *implicit topology* stuff doesn't fly, because there is no guarantee
that all endpoints will always all point to the same controller.
Quoted 3 lines
The local interrupts (per-CPU) are always managed by the INTC. The interrupt controllers to manage device interrupts (such as PLIC) can vary from platform to platform and have INTC as the parent domain.
I don't know how to make it clearer: this isn't about the situation *today*. It is about what you will have two or five years from now.
Relying on a default topology is stupidly bad, and you will end-up in a terrible corner eventually, because you can't have *two* defaults.
Quoted 17 lines
We already have high-end interrupt controllers (such as AIA) under development which are scalable for server-grade SoC, mobile SoC and various other types of SoCs.
We are able to describe the topology of different types of interrupt controllers (PLIC as well as AIA) in DT.
The only issue is for drivers which do not have dedicated DT node (such as SBI IPI, SBI Timer, SBI PMU, or KVM RISC-V) but the upside is that local interrupt numbers used by these drivers is clearly defined by the RISC-V ISA specification:
Here are the local interrupts defined by the RISC-V ISA spec:
IRQ13 => PMU overflow interrupt (used by SBI PMU driver) IRQ12 => S-mode guest external interrupt (to be used by KVM RISC-V) IRQ11 => M-mode external interrupt (used by firmware)
Quoted 5 lines
IRQ9 => S-mode external interrupt (used by PLIC driver) IRQ7 => M-mode timer interrupt IRQ5 => S-mode timer interrupt (used by SBI Timer driver) IRQ3 => M-mode software interrupt (used by firmware)IRQ1 => S-mode software interrupt (used by SBI IPI driver)
Again, you are missing the point. It isn't about the interrupt number (nobody gives a crap about them). It is about the entity the device is connected to. No amount of copy pasting of the spec changes that.
Quoted 91 lines
Quoted 58 lines
Quoted 53 lines
Quoted 5 lines
what you should have instead is something like:
static struct
fwnode_handle*(*__get_root_intc_node)(void); structfwnode_handle*riscv_get_root_intc_hwnode(void)Quoted 8 lines
{ if (__get_root_intc_node) return __get_root_intc_node(); return NULL; }and the corresponding registration interface.
Thanks, I will follow this suggestion. This is a much better approach and it will avoid touching existing drivers.
Quoted 36 lines
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for
duplicate entries).Quoted 12 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );This is what I'm talking about. It is simply broken. So either you don't
need a per-CPU node (and the DT was bad the first place), or you absolutely need
one (and the whole 'well-known/default domain' doesn't work at all).Quoted 4 lines
Quoted 1 line
Either way, this patch is plain wrong.
Okay, I will update this patch with the new approach which you suggested.
Quoted 8 lines
But how do you plan to work around the fact that everything is currently build around having a node (and an irqdomain) per CPU? The PLIC, for example,
clearly has one parent per CPU, not one global parent.I'm sure there was a good reason for this, and I suspect merging the domains
will simply end up breaking things.We can have multiple PLIC instances in a platform and each PLIC instance targets a subset of CPUs. Further, each PLIC instance has multiple PLIC contexts for associated CPUs.
The per-CPU INTC DT nodes and the "interrupts-extended" DT property of PLIC DT node helps us describe the association between various PLIC contexts and CPUs.
Here's an example PLIC DT node:
plic: interrupt-controller@c000000 { #address-cells = <0>; #interrupt-cells = <1>; compatible = "sifive,fu540-c000-plic", "sifive,plic-1.0.0"; interrupt-controller; interrupts-extended = <&cpu0_intc 11>, <&cpu1_intc 11>, <&cpu1_intc 9>, <&cpu2_intc 11>, <&cpu2_intc 9>, <&cpu3_intc 11>, <&cpu3_intc 9>, <&cpu4_intc 11>, <&cpu4_intc 9>; reg = <0xc000000 0x4000000>; riscv,ndev = <10>; };
Quoted 8 lines
In above above example, PLIC has 9 contexts and context to CPU connections are as follows:
PLIC context0 => CPU0 M-mode external interrupt PLIC context1 => CPU1 M-mode external interrupt PLIC context2 => CPU1 S-mode external interrupt PLIC context3 => CPU2 M-mode external interrupt PLIC context4 => CPU2 S-mode external interrupt
....
Asymmetric interrupt routing. How lovely. How broken.
Quoted 7 lines
This is just one example and we can describe any kind of PLIC context to CPU connections using "interrupts-extended" DT property.
The same level of flexibility is provided by AIA interrupt controllers which are under development.
How promising. I really hope someone will eventually barge in and clean this mess.
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
Re: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
In reply to Jessica ClarkeQuoted 30 lines · Jessica Clarke
Quoted 7 lines · Marc Zyngier
But how do you plan to work around the fact that everything is currently build around having a node (and an irqdomain) per CPU? The PLIC, for example, clearly has one parent per CPU, not one global parent.
I'm sure there was a good reason for this, and I suspect merging the domains will simply end up breaking things.
On the contrary, the drivers rely on the controller being the same across all harts, with
riscv_intc_initskipping initialisation for all but the boot hart’s controller. The bindings are a complete pain to deal with as a result, what you *want* is like you have in the Arm world where there is just one interrupt controller in the device tree with some of the interrupts per-processor, but instead we have this overengineered nuisance. The only reason there are per-hart interrupt controllers is because that’s how the contexts for the CLINT/PLIC are specified, but that really should have been done another way rather than abusing the interrupts-extended property for that. In the FreeBSD world we’ve been totally ignoring the device tree nodes for the local interrupt controllers but for my AIA and ACLINT branch I started a few months ago (though ACLINT's now been completely screwed up by RVI politics, things have been renamed and split up differently in the past few days and software interrupts de-prioritised with no current path to ratification, so that was a waste of my time) I just hang the driver off the boot hart’s node and leave all the others as totally ignored and a waste of space other than to figure out the contexts for the PLIC etc.
Quoted 2 lines
TL;DR yes the bindings are awful, no there’s no issue with merging the domains.
I don't know how that flies with something like[1], where CPU0 only gets interrupts in M-Mode and not S-Mode. Maybe it doesn't really matter, but this sort of asymmetric routing is totally backward.
It sometime feels like the RV folks are actively trying to make this architecture a mess... :-/
M.
[1] CAAhSdy0jTTDzoc+3T_8uLiWfBN3AFCWj99Ayc-Yh8FBfzUY2sQ@mail.gmail.com
Signature · 1 line
Without deviation from the norm, progress is not possible.
Anup Patel
maintainerRe: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
In reply to Marc ZyngierQuoted 125 lines · Marc Zyngier
Quoted 89 lines · Anup Patel
Quoted 66 lines · Marc Zyngier
Quoted 64 lines · Anup Patel
Quoted 45 lines · Marc Zyngier
Quoted 43 lines · Anup Patel
We should create INTC domain using a synthetic fwnode which will allow drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, RISC-V PMU driver, etc) not having dedicated DT/ACPI node to directly create interrupt mapping for standard local interrupt numbers defined by the RISC-V privileged specification.
Signed-off-by Anup Patel <[email protected]>--- arch/riscv/include/asm/irq.h | 2 ++ arch/riscv/kernel/irq.c | 13 +++++++++++++ drivers/clocksource/timer-clint.c | 13 +++++++------ drivers/clocksource/timer-riscv.c | 11 ++--------- drivers/irqchip/irq-riscv-intc.c | 12 ++++++++++-- drivers/irqchip/irq-sifive-plic.c | 19 +++++++++++-------- 6 files changed, 45 insertions(+), 25 deletions(-)arch/riscv/include/asm/irq.h +2
-0@@ -12,6 +12,8 @@#include <asm-generic/irq.h> +extern struct fwnode_handle *riscv_intc_fwnode (void ); +extern void __init init_IRQ (void );#endif /* _ASM_RISCV_IRQ_H */ arch/riscv/kernel/irq.c +2
-0@@ -7,9 +7,22 @@#include <linux/interrupt.h> #include <linux/irqchip.h> +#include <linux/irqdomain.h> +#include <linux/module.h> #include <linux/seq_file.h> #include <asm/smp.h> Quoted 15 lines
arch/riscv/kernel/irq.c line 24
Quoted 10 lines
arch/riscv/kernel/irq.c +10
-0+static struct fwnode_handle *intc_fwnode; + +struct fwnode_handle *riscv_intc_fwnode (void ) +{ +if (!intc_fwnode) + intc_fwnode =irq_domain_alloc_named_fwnode ("RISCV-INTC" ); + +return intc_fwnode; +} +EXPORT_SYMBOL_GPL (riscv_intc_fwnode);Why is this created outside of the root interrupt controller driver? Furthermore, why do you need to create a new fwnode the first place? As far as I can tell, the INTC does have a node, and what you don't have is the firmware linkage between PMU (an others) and the INTC.
Fair enough, I will update this patch to not create a synthetic fwnode.
Quoted 7 lines
Quoted 3 lines
The issue is not with INTC driver. We have other drivers and places (such as SBI IPI driver, SBI PMU driver, and KVM RISC-V AIA support) where we don't have a way to locate INTC fwnode.
And that's exactly what I am talking about: The INTC is OK (sort of), but the firmware is too crap for words, and isn't even able to expose where the various endpoints route their interrupts to.
The firmware is always present at a higher privilege-level hence there is no DT node to discover the presence of firmware. The local interrupts
used by the firmware for IPI, Timer and PMU are defined by the RISC-V ISA specification.Quoted 7 lines
Yes, this is probably fine today because you can describe the topology of RISC-V systems on the surface of a post stamp. Once you get to the complexity of a server-grade SoC (or worse, a mobile phone style SoC), this *implicit topology* stuff doesn't fly, because there is no guarantee
that all endpoints will always all point to the same controller.Quoted 3 lines
The local interrupts (per-CPU) are always managed by the INTC. The interrupt controllers to manage device interrupts (such as PLIC) can vary from platform to platform and have INTC as the parent domain.
I don't know how to make it clearer: this isn't about the situation *today*. It is about what you will have two or five years from now.
Relying on a default topology is stupidly bad, and you will end-up in a terrible corner eventually, because you can't have *two* defaults.
Quoted 17 lines
We already have high-end interrupt controllers (such as AIA) under development which are scalable for server-grade SoC, mobile SoC and various other types of SoCs.
We are able to describe the topology of different types of interrupt controllers (PLIC as well as AIA) in DT.
The only issue is for drivers which do not have dedicated DT node (such as SBI IPI, SBI Timer, SBI PMU, or KVM RISC-V) but the upside is that local interrupt numbers used by these drivers is clearly defined by the RISC-V ISA specification:
Here are the local interrupts defined by the RISC-V ISA spec:
IRQ13 => PMU overflow interrupt (used by SBI PMU driver) IRQ12 => S-mode guest external interrupt (to be used by KVM RISC-V) IRQ11 => M-mode external interrupt (used by firmware)Quoted 5 lines
IRQ9 => S-mode external interrupt (used by PLIC driver) IRQ7 => M-mode timer interrupt IRQ5 => S-mode timer interrupt (used by SBI Timer driver) IRQ3 => M-mode software interrupt (used by firmware)IRQ1 => S-mode software interrupt (used by SBI IPI driver)
Quoted 4 lines
Again, you are missing the point. It isn't about the interrupt number (nobody gives a crap about them). It is about the entity the device is connected to. No amount of copy pasting of the spec changes that.
The INTC CSRs are part of the RISC-V privileged specification and maintaining backward compatibility is of utmost importance in RISC-V ISA so I don't see why per-CPU INTC will be replaced by something totally incompatible in future.
Quoted 102 lines
Quoted 93 lines
Quoted 65 lines
Quoted 54 lines
Quoted 6 lines
what you should have instead is something like:
static struct
fwnode_handle*(*__get_root_intc_node)(void); structfwnode_handle*riscv_get_root_intc_hwnode(void)Quoted 8 lines
{ if (__get_root_intc_node) return __get_root_intc_node(); return NULL; }and the corresponding registration interface.
Thanks, I will follow this suggestion. This is a much better approach and it will avoid touching existing drivers.
Quoted 36 lines
But either way, something breaks: the INTC has one node per CPU, and expect one irqdomain per CPU. Having a single fwnode completely breaks the INTC driver (and probably the irqdomain list, as we don't check for
duplicate entries).Quoted 12 lines
drivers/irqchip/irq-riscv-intc.c +0
-2@@ -112,8 +112,16 @@ static int __init riscv_intc_init(struct device_node *node, if (riscv_hartid_to_cpuid(hartid) != smp_processor_id())return 0 ; - intc_domain =irq_domain_add_linear (node,BITS_PER_LONG , - &riscv_intc_domain_ops,NULL );drivers/irqchip/irq-riscv-intc.c static int __init riscv_intc_init(struct · line 125
Quoted 10 lines
drivers/irqchip/irq-riscv-intc.c +10
-0+/* +* Create INTC domain using a synthetic fwnode which will allow +* drivers (such as RISC-V SBI IPI driver, RISC-V timer driver, +* RISC-V PMU driver, etc) not having dedicated DT/ACPI node to +* directly create interrupt mapping for standard local interrupt +* numbers defined by the RISC-V privileged specification. +*/ + intc_domain =irq_domain_create_linear (riscv_intc_fwnode (), +BITS_PER_LONG , + &riscv_intc_domain_ops,NULL );This is what I'm talking about. It is simply broken. So either you don't
need a per-CPU node (and the DT was bad the first place), or you absolutely need
one (and the whole 'well-known/default domain' doesn't work at all).Quoted 4 lines
Quoted 1 line
Either way, this patch is plain wrong.
Okay, I will update this patch with the new approach which you suggested.
But how do you plan to work around the fact that everything is currently
build around having a node (and an irqdomain) per CPU? The PLIC, for example,
clearly has one parent per CPU, not one global parent.Quoted 3 lines
I'm sure there was a good reason for this, and I suspect merging the domains
will simply end up breaking things.We can have multiple PLIC instances in a platform and each PLIC instance targets a subset of CPUs. Further, each PLIC instance has multiple PLIC contexts for associated CPUs.
The per-CPU INTC DT nodes and the "interrupts-extended" DT property of PLIC DT node helps us describe the association between various PLIC contexts and CPUs.
Here's an example PLIC DT node:
plic: interrupt-controller@c000000 { #address-cells = <0>; #interrupt-cells = <1>; compatible = "sifive,fu540-c000-plic", "sifive,plic-1.0.0"; interrupt-controller; interrupts-extended = <&cpu0_intc 11>, <&cpu1_intc 11>, <&cpu1_intc 9>, <&cpu2_intc 11>, <&cpu2_intc 9>, <&cpu3_intc 11>, <&cpu3_intc 9>, <&cpu4_intc 11>, <&cpu4_intc 9>; reg = <0xc000000 0x4000000>; riscv,ndev = <10>; };Quoted 8 lines
In above above example, PLIC has 9 contexts and context to CPU connections are as follows:
PLIC context0 => CPU0 M-mode external interrupt PLIC context1 => CPU1 M-mode external interrupt PLIC context2 => CPU1 S-mode external interrupt PLIC context3 => CPU2 M-mode external interrupt PLIC context4 => CPU2 S-mode external interrupt
....
Quoted 1 line
Asymmetric interrupt routing. How lovely. How broken.
This is a known issue with PLIC where contexts from the same PLIC can target both M-mode and S-mode. This asymmetric interrupt routing is not there in under-development AIA.
Quoted 11 lines
Quoted 8 lines
This is just one example and we can describe any kind of PLIC context to CPU connections using "interrupts-extended" DT property.
The same level of flexibility is provided by AIA interrupt controllers which are under development.
How promising. I really hope someone will eventually barge in and clean this mess.
The INTC DT node being per-CPU is the only strange thing in RISC-V but we can't change INTC DT bindings at this stage.
Apart from this, I still don't see anything messy here.
Regards,
Anup
Quoted 4 lines
M.--
Jazz is not dead. It just smells funny...
Anup Patel
maintainerRe: [PATCH v2 2/6] irqchip/riscv-intc: Create domain using named fwnode
In reply to Marc ZyngierQuoted 33 lines · Marc Zyngier
Quoted 30 lines · Jessica Clarke
Quoted 7 lines · Marc Zyngier
But how do you plan to work around the fact that everything is currently build around having a node (and an irqdomain) per CPU? The PLIC, for example, clearly has one parent per CPU, not one global parent.
I'm sure there was a good reason for this, and I suspect merging the domains will simply end up breaking things.
On the contrary, the drivers rely on the controller being the same across all harts, with
riscv_intc_initskipping initialisation for all but the boot hart’s controller. The bindings are a complete pain to deal with as a result, what you *want* is like you have in the Arm world where there is just one interrupt controller in the device tree with some of the interrupts per-processor, but instead we have this overengineered nuisance. The only reason there are per-hart interrupt controllers is because that’s how the contexts for the CLINT/PLIC are specified, but that really should have been done another way rather than abusing the interrupts-extended property for that. In the FreeBSD world we’ve been totally ignoring the device tree nodes for the local interrupt controllers but for my AIA and ACLINT branch I started a few months ago (though ACLINT's now been completely screwed up by RVI politics, things have been renamed and split up differently in the past few days and software interrupts de-prioritised with no current path to ratification, so that was a waste of my time) I just hang the driver off the boot hart’s node and leave all the others as totally ignored and a waste of space other than to figure out the contexts for the PLIC etc.
Quoted 6 lines
Quoted 2 lines
TL;DR yes the bindings are awful, no there’s no issue with merging the domains.
I don't know how that flies with something like[1], where CPU0 only gets interrupts in M-Mode and not S-Mode. Maybe it doesn't really matter, but this sort of asymmetric routing is totally backward.
The example PLIC DT node which I provided is from SiFive FU540, where we have 5 CPUs. The CPU0 in FU540 is a cache-coherent microcontroller having only M-mode (i.e. No MMU hence not Linux capable).
Quoted 3 lines
It sometime feels like the RV folks are actively trying to make this architecture a mess... :-/
Well, I still fail to understand what is messy here.
Regards,
Anup
Quoted 7 lines
M.[1] CAAhSdy0jTTDzoc+3T_8uLiWfBN3AFCWj99Ayc-Yh8FBfzUY2sQ@mail.gmail.com
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv