|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v2 04/10] xen/arm/irq: add handling for IRQs in the eSPI range
Hi, On 21/08/2025 16:59, Volodymyr Babchuk wrote: > I believe that runtime check for GICD_TYPER.ESPI should be sufficient,> but maintainers can correct me there.Leonid Komarianskyi <Leonid_Komarianskyi@xxxxxxxx> writes:Currently, Xen does not support eSPI interrupts, leading to a data abort when such interrupts are defined in the DTS. This patch introduces a separate array to initialize up to 1024 interrupt descriptors in the eSPI range and adds the necessary defines and helper function. These changes lay the groundwork for future implementation of full eSPI interrupt support. As this GICv3.1 feature is not required by all vendors, all changes are guarded by ifdefs, depending on the corresponding Kconfig option.I don't think that it is a good idea to hide this feature under Kconfig option, as this will increase number of different build variants. I haven't seen many board with ESPI available. So I think it would be better if this is under a Kconfig because not everyone may want to have the code. [...]
By how much will this increase the Xen binary? This is really confusing. Should it be something like espi_desc[NR_ESPI_IRQS]? +1. Cheers, -- Julien Grall
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |